Skip to content

Commit 14768e3

Browse files
Merge pull request #2209 from amanchopra1905/stage
HYP Release Updates
2 parents 79da3ae + fff6206 commit 14768e3

10 files changed

+120
-31
lines changed
-522 KB
Loading
-574 KB
Loading
-181 KB
Loading
58.9 KB
Loading

docs/autoheal-with-hooks.md

Lines changed: 29 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -86,44 +86,44 @@ LT_USERNAME = os.getenv('LT_USERNAME')
8686
LT_ACCESS_KEY = os.getenv('LT_ACCESS_KEY')
8787

8888
desired_cap_chrome = {
89-
"build" : "Lambdatest Build 2",
90-
"name" : "Autoheal Test via Hooks",
91-
"platform" : "Windows 10",
92-
"browserName" : "Chrome",
93-
"version" : "latest",
94-
"visual" : False,
95-
"video" : True,
96-
"network": True,
97-
"console": True,
98-
'goog:chromeOptions': {'args': ['--window-size=400x300']},
89+
"build" : "Lambdatest Build 2",
90+
"name" : "Autoheal Test via Hooks",
91+
"platform" : "Windows 10",
92+
"browserName" : "Chrome",
93+
"version" : "latest",
94+
"visual" : False,
95+
"video" : True,
96+
"network": True,
97+
"console": True,
98+
'goog:chromeOptions': {'args': ['--window-size=400x300']},
9999
}
100100

101101
hub = f"https://{LT_USERNAME}:{LT_ACCESS_KEY}@hub.lambdatest.com/wd/hub"
102102

103103
def OneTest(caps, sleepTime):
104-
begin = time.time()
105-
driver = webdriver.Remote(command_executor=hub, desired_capabilities=caps)
106-
end = time.time()
107-
print(f"Startup time for {caps['browserName']} {end - begin} , {begin} , {end}")
108-
driver.get("https://www.selenium.dev")
109-
time.sleep(sleepTime)
104+
begin = time.time()
105+
driver = webdriver.Remote(command_executor=hub, desired_capabilities=caps)
106+
end = time.time()
107+
print(f"Startup time for {caps['browserName']} {end - begin} , {begin} , {end}")
108+
driver.get("https://www.selenium.dev")
109+
time.sleep(sleepTime)
110110

111-
driver.execute_script('lambdatest_executor:{"action":"lambda-heal-start"}') #start hook for autoheal
111+
driver.execute_script('lambdatest_executor:{"action":"lambda-heal-start"}') #start hook for autoheal
112112

113-
driver.find_element_by_id('td-block-1')
114-
driver.execute_script("document.getElementById(\"td-block-1\").id=\"updatedtd-block-1\";")
115-
driver.find_element_by_id('updatedtd-block-1')
116-
driver.find_element_by_id("td-block-1")
113+
driver.find_element_by_id('td-block-1')
114+
driver.execute_script("document.getElementById(\"td-block-1\").id=\"updatedtd-block-1\";")
115+
driver.find_element_by_id('updatedtd-block-1')
116+
driver.find_element_by_id("td-block-1")
117117

118-
driver.execute_script('lambdatest_executor:{"action":"lambda-heal-stop"}') #stop hook for autoheal
118+
driver.execute_script('lambdatest_executor:{"action":"lambda-heal-stop"}') #stop hook for autoheal
119119

120-
driver.execute_script("console.log('Test started');")
121-
driver.execute_script("console.info('Navigated to selenium.dev');")
122-
driver.execute_script("console.warn('This is a warning message');")
123-
driver.execute_script("console.error('This is an error message');")
124-
driver.execute_script("console.debug('Debugging test flow');")
125-
driver.execute_script("console.log('Test completed successfully');")
126-
driver.quit()
120+
driver.execute_script("console.log('Test started');")
121+
driver.execute_script("console.info('Navigated to selenium.dev');")
122+
driver.execute_script("console.warn('This is a warning message');")
123+
driver.execute_script("console.error('This is an error message');")
124+
driver.execute_script("console.debug('Debugging test flow');")
125+
driver.execute_script("console.log('Test completed successfully');")
126+
driver.quit()
127127

128128
OneTest(desired_cap_chrome, 5)
129129
```

docs/hyperexecute-auto-healing.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,22 @@ const capability = {
7878

7979
Auto Healing employs a dynamic locator strategy that adapts to DOM (Document Object Model) changes in real-time. When an element is initially located, the system records its DOM path and associated attributes. If subsequent attempts to find the element fail due to application updates, the Auto Healing mechanism activates. It analyzes the current DOM structure, comparing it against the previously recorded state, and generates new, contextually relevant locators by intelligently combining element attributes and hierarchical information. This process occurs seamlessly during test runtime, allowing scripts to continue execution despite locator changes. The system continuously monitors the web page for DOM modifications, ensuring sustained test reliability even in the face of frequent application updates.
8080

81+
## Using AutoHeal with Hooks
82+
83+
In addition to enabling AutoHeal globally through capabilities, HyperExecute also supports **AutoHeal Hooks** for fine-grained control during test execution.
84+
85+
These hooks allow you to **start or stop the AutoHeal mechanism dynamically** at any point within your Selenium test scripts. This is especially useful when only certain test steps involve dynamic elements or frequently changing locators.
86+
87+
By using these hooks, you can:
88+
- Start AutoHeal before performing actions on elements likely to change.
89+
- Stop AutoHeal immediately after those interactions are completed.
90+
- Ensure the rest of your test executes with standard Selenium behavior.
91+
92+
This provides precise control over when element healing should be applied, improving reliability and reducing flakiness without impacting unrelated steps.
93+
94+
> To learn how to use AutoHeal hooks in your Selenium scripts, refer to the detailed guide: [How to Use AutoHeal using Hooks](/support/docs/autoheal-with-hooks/)
95+
96+
8197
## Benefits of Auto Healing
8298
Here are some of the benefits of using HyperExecute's Auto Healing feature:
8399

@@ -100,3 +116,4 @@ By following these best practices, you can use auto healing to improve the relia
100116
- Configure auto healing to retry tests a limited number of times. This will help to prevent infinite loops and resource exhaustion.
101117
- Log all Auto Healing activity. This will help you understand why tests are failing and to troubleshoot any problems that occur.
102118
- Monitor the effectiveness of Auto Healing. Track the number of tests that are healed and the number of false positives. This will help you to determine whether or not auto healing is providing a net benefit.
119+

docs/hyperexecute-release-notes-3-0-6.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,8 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
4343
})
4444
}}
4545
></script>
46-
## Feature: HyperExecute Logs Categorization
47-
Debugging large test executions often generates extensive logs, making it difficult to identify key issues. The new **Logs Categorization** feature enhances log readability by automatically highlighting and grouping critical entries.
46+
## Feature: HyperExecute Logs Highlights
47+
Debugging large test executions often generates extensive logs, making it difficult to identify key issues. The new **Logs Highlights** feature enhances log readability by automatically highlighting and grouping critical entries.
4848

4949
HyperExecute categorizes logs into Errors and Warnings using intelligent pattern detection based on regular expressions (regex). This will help you quickly locate and review the most relevant log lines during test analysis.
5050

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
id: hyperexecute-release-notes-3-0-8
3+
title: Version 3.0.8
4+
hide_title: false
5+
sidebar_label: Version 3.0.8
6+
description: Version 3.0.8
7+
keywords:
8+
- LambdaTest Hyperexecute
9+
- LambdaTest Hyperexecute help
10+
- LambdaTest Hyperexecute documentation
11+
- FAQs
12+
url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-0-8/
13+
site_name: LambdaTest
14+
slug: hyperexecute-release-notes-3-0-8/
15+
---
16+
17+
import NewReleaseTag from '../src/component/newRelease.js';
18+
import EnhancementTag from '../src/component/enhancementTag';
19+
import BugFixTag from '../src/component/bugFixTag';
20+
import CodeBlock from '@theme/CodeBlock';
21+
import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
22+
23+
<script type="application/ld+json"
24+
dangerouslySetInnerHTML={{ __html: JSON.stringify({
25+
"@context": "https://schema.org",
26+
"@type": "BreadcrumbList",
27+
"itemListElement": [{
28+
"@type": "ListItem",
29+
"position": 1,
30+
"name": "Home",
31+
"item": "https://www.lambdatest.com"
32+
},{
33+
"@type": "ListItem",
34+
"position": 2,
35+
"name": "Support",
36+
"item": "https://www.lambdatest.com/support/docs/"
37+
},{
38+
"@type": "ListItem",
39+
"position": 3,
40+
"name": "Version",
41+
"item": "https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-0-8/"
42+
}]
43+
})
44+
}}
45+
></script>
46+
47+
## Job Insights View in HyperExecute
48+
With the Job Insights View, you can now access a comprehensive overview of all your test results across different configurations, all in one unified interface, Even when tests are split across multiple environments or parallel jobs, HyperExecute intelligently aggregates the data, giving you a complete, consolidated view of your job performance.
49+
50+
This feature empowers you to:
51+
52+
- **Compare results across configurations** effortlessly.
53+
- **Review job summaries and outcomes** in a single glance.
54+
- **Analyze historical job runs** within the same project to identify patterns, regressions, or performance drifts quickly.
55+
56+
The **Job Insights View** is especially valuable for teams running the same tests across multiple combinations (such as different browsers, OS versions, or device types). It helps you pinpoint inconsistencies and regressions instantly, enabling faster decision-making and smoother test management.
57+
58+
<img loading="lazy" src={require('../assets/images/hyperexecute/release-notes/test-insights.png').default} alt="Image" className="doc_img"/>

docs/hyperexecute-release-notes.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,15 @@ HyperExecute is an AI Native Test Orchestration Cloud Platform, enabling test au
5656
| [Version 1.0.0](/support/docs/hyperexecute-mcp-server-release-notes-1-0-0) | May 28, 2025|
5757

5858
### 2025 releases
59+
#### October, 2025
60+
| Release Number | Release Date |
61+
|----------------|--------------|
62+
| [Version 3.0.8](/support/docs/hyperexecute-release-notes-3-0-8) | Oct 13, 2025|
63+
5964
#### September, 2025
6065
| Release Number | Release Date |
6166
|----------------|--------------|
67+
| [Version 3.0.6](/support/docs/hyperexecute-release-notes-3-0-6) | Sept 29, 2025|
6268
| [Version 3.0.4](/support/docs/hyperexecute-release-notes-3-0-4) | Sept 15, 2025|
6369
| [Version 3.0.3](/support/docs/hyperexecute-release-notes-3-0-3) | Sept 08, 2025|
6470

sidebars.js

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -925,6 +925,14 @@ module.exports = {
925925
collapsed: true,
926926
label: "2025 Releases",
927927
items: [
928+
{
929+
type: "category",
930+
collapsed: true,
931+
label: "October, 2025",
932+
items: [
933+
"hyperexecute-release-notes-3-0-8",
934+
],
935+
},
928936
{
929937
type: "category",
930938
collapsed: true,

0 commit comments

Comments
 (0)