diff --git a/assets/images/analytics/test-intelligence-ai-test-rca-configuration.png b/assets/images/analytics/test-intelligence-ai-test-rca-configuration.png new file mode 100644 index 00000000..5249c00e Binary files /dev/null and b/assets/images/analytics/test-intelligence-ai-test-rca-configuration.png differ diff --git a/assets/images/analytics/test-intelligence-ai-test-rca-insights.png b/assets/images/analytics/test-intelligence-ai-test-rca-insights.png new file mode 100644 index 00000000..d6078a30 Binary files /dev/null and b/assets/images/analytics/test-intelligence-ai-test-rca-insights.png differ diff --git a/assets/images/analytics/test-intelligence-ai-test-rca-widget.png b/assets/images/analytics/test-intelligence-ai-test-rca-widget.png new file mode 100644 index 00000000..33b8656e Binary files /dev/null and b/assets/images/analytics/test-intelligence-ai-test-rca-widget.png differ diff --git a/assets/images/hyperexecute/release-notes/test-insights.png b/assets/images/hyperexecute/release-notes/test-insights.png new file mode 100644 index 00000000..2a4e0bfb Binary files /dev/null and b/assets/images/hyperexecute/release-notes/test-insights.png differ diff --git a/docs/autoheal-with-hooks.md b/docs/autoheal-with-hooks.md index 74a98d07..6a8e81ed 100644 --- a/docs/autoheal-with-hooks.md +++ b/docs/autoheal-with-hooks.md @@ -83,42 +83,44 @@ from selenium import webdriver platform = os.getenv('HYPEREXECUTE_PLATFORM') desired_cap_chrome = { - "build": "Lambdatest Build 2", - "name": "Lambdatest Test", - "platform": platform, - "browserName": "Chrome", - "version": "latest", - "visual": False, - "video": True, - "network": True, - "console": True, - 'goog:chromeOptions': {'args': ['--window-size=400x300']}, + "build" : "Lambdatest Build 2", + "name" : "Autoheal Test via Hooks", + "platform" : "Windows 10", + "browserName" : "Chrome", + "version" : "latest", + "visual" : False, + "video" : True, + "network": True, + "console": True, + 'goog:chromeOptions': {'args': ['--window-size=400x300']}, } hub = f"https://{os.getenv('LT_USERNAME')}:{os.getenv('LT_ACCESS_KEY')}@hub.lambdatest.com/wd/hub" -def test_autoheal(caps, sleep_time=5): - driver = webdriver.Remote(command_executor=hub, desired_capabilities=caps) - - # Navigate to page - driver.get("https://www.selenium.dev") - - # ===== Autoheal START ===== - driver.execute_script('lambdatest_executor:{"action":"lambda-heal-start"}') - - # Interact with elements that may change dynamically - driver.find_element_by_id('td-block-1') - driver.execute_script('document.getElementById("td-block-1").id="updatedtd-block-1";') - driver.find_element_by_id('updatedtd-block-1') - - # ===== Autoheal STOP ===== - driver.execute_script('lambdatest_executor:{"action":"lambda-heal-stop"}') - - # Continue normal test steps - driver.execute_script("console.log('Test completed successfully');") - driver.execute_script("lambda-status=passed") +def OneTest(caps, sleepTime): + begin = time.time() + driver = webdriver.Remote(command_executor=hub, desired_capabilities=caps) + end = time.time() + print(f"Startup time for {caps['browserName']} {end - begin} , {begin} , {end}") + driver.get("https://www.selenium.dev") + time.sleep(sleepTime) + + driver.execute_script('lambdatest_executor:{"action":"lambda-heal-start"}') #start hook for autoheal + + driver.find_element_by_id('td-block-1') + driver.execute_script("document.getElementById(\"td-block-1\").id=\"updatedtd-block-1\";") + driver.find_element_by_id('updatedtd-block-1') + driver.find_element_by_id("td-block-1") + + driver.execute_script('lambdatest_executor:{"action":"lambda-heal-stop"}') #stop hook for autoheal - driver.quit() + driver.execute_script("console.log('Test started');") + driver.execute_script("console.info('Navigated to selenium.dev');") + driver.execute_script("console.warn('This is a warning message');") + driver.execute_script("console.error('This is an error message');") + driver.execute_script("console.debug('Debugging test flow');") + driver.execute_script("console.log('Test completed successfully');") + driver.quit() test_autoheal(desired_cap_chrome) ``` diff --git a/docs/hyperexecute-auto-healing.md b/docs/hyperexecute-auto-healing.md index 344fbd5f..01bcd34a 100644 --- a/docs/hyperexecute-auto-healing.md +++ b/docs/hyperexecute-auto-healing.md @@ -78,6 +78,22 @@ const capability = { 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. +## Using AutoHeal with Hooks + +In addition to enabling AutoHeal globally through capabilities, HyperExecute also supports **AutoHeal Hooks** for fine-grained control during test execution. + +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. + +By using these hooks, you can: +- Start AutoHeal before performing actions on elements likely to change. +- Stop AutoHeal immediately after those interactions are completed. +- Ensure the rest of your test executes with standard Selenium behavior. + +This provides precise control over when element healing should be applied, improving reliability and reducing flakiness without impacting unrelated steps. + +> 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/) + + ## Benefits of Auto Healing Here are some of the benefits of using HyperExecute's Auto Healing feature: @@ -100,3 +116,4 @@ By following these best practices, you can use auto healing to improve the relia - Configure auto healing to retry tests a limited number of times. This will help to prevent infinite loops and resource exhaustion. - Log all Auto Healing activity. This will help you understand why tests are failing and to troubleshoot any problems that occur. - 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. + diff --git a/docs/hyperexecute-release-notes-3-0-6.md b/docs/hyperexecute-release-notes-3-0-6.md index 59f2637d..beb5f8d4 100644 --- a/docs/hyperexecute-release-notes-3-0-6.md +++ b/docs/hyperexecute-release-notes-3-0-6.md @@ -43,8 +43,8 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co }) }} > -## Feature: HyperExecute Logs Categorization -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. +## Feature: HyperExecute Logs Highlights +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. 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. diff --git a/docs/hyperexecute-release-notes-3-0-8.md b/docs/hyperexecute-release-notes-3-0-8.md new file mode 100644 index 00000000..7c65f5da --- /dev/null +++ b/docs/hyperexecute-release-notes-3-0-8.md @@ -0,0 +1,58 @@ +--- +id: hyperexecute-release-notes-3-0-8 +title: Version 3.0.8 +hide_title: false +sidebar_label: Version 3.0.8 +description: Version 3.0.8 +keywords: + - LambdaTest Hyperexecute + - LambdaTest Hyperexecute help + - LambdaTest Hyperexecute documentation + - FAQs +url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-0-8/ +site_name: LambdaTest +slug: hyperexecute-release-notes-3-0-8/ +--- + +import NewReleaseTag from '../src/component/newRelease.js'; +import EnhancementTag from '../src/component/enhancementTag'; +import BugFixTag from '../src/component/bugFixTag'; +import CodeBlock from '@theme/CodeBlock'; +import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys"; + + + +## Job Insights View in HyperExecute +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. + +This feature empowers you to: + +- **Compare results across configurations** effortlessly. +- **Review job summaries and outcomes** in a single glance. +- **Analyze historical job runs** within the same project to identify patterns, regressions, or performance drifts quickly. + +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. + +Image \ No newline at end of file diff --git a/docs/hyperexecute-release-notes.md b/docs/hyperexecute-release-notes.md index 7ea23338..682261e6 100644 --- a/docs/hyperexecute-release-notes.md +++ b/docs/hyperexecute-release-notes.md @@ -62,9 +62,15 @@ HyperExecute is an AI Native Test Orchestration Cloud Platform, enabling test au | [Version 1.0.0](/support/docs/hyperexecute-mcp-server-release-notes-1-0-0) | May 28, 2025| ### 2025 releases +#### October, 2025 +| Release Number | Release Date | +|----------------|--------------| +| [Version 3.0.8](/support/docs/hyperexecute-release-notes-3-0-8) | Oct 13, 2025| + #### September, 2025 | Release Number | Release Date | |----------------|--------------| +| [Version 3.0.6](/support/docs/hyperexecute-release-notes-3-0-6) | Sept 29, 2025| | [Version 3.0.4](/support/docs/hyperexecute-release-notes-3-0-4) | Sept 15, 2025| | [Version 3.0.3](/support/docs/hyperexecute-release-notes-3-0-3) | Sept 08, 2025| diff --git a/sidebars.js b/sidebars.js index 88bd669d..42574ade 100644 --- a/sidebars.js +++ b/sidebars.js @@ -923,6 +923,14 @@ module.exports = { collapsed: true, label: "2025 Releases", items: [ + { + type: "category", + collapsed: true, + label: "October, 2025", + items: [ + "hyperexecute-release-notes-3-0-8", + ], + }, { type: "category", collapsed: true,