diff --git a/docs/hyperexecute-release-notes-2-7-0.md b/docs/hyperexecute-release-notes-2-7-0.md new file mode 100644 index 000000000..06ac50235 --- /dev/null +++ b/docs/hyperexecute-release-notes-2-7-0.md @@ -0,0 +1,51 @@ +--- +id: hyperexecute-release-notes-2-7-0 +title: Version 2.7.0 +hide_title: false +sidebar_label: Version 2.7.0 +description: Version 2.7.0 +keywords: + - LambdaTest Hyperexecute + - LambdaTest Hyperexecute help + - LambdaTest Hyperexecute documentation + - FAQs +url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-2-7-0/ +site_name: LambdaTest +slug: hyperexecute-release-notes-2-7-0/ +--- + +import NewReleaseTag from '../src/component/newRelease.js'; +import EnhancementTag from '../src/component/enhancementTag'; +import BugFixTag from '../src/component/bugFixTag'; + + +## Browser Version Updates: + +- **Firefox :** Added support for Firefox-133, and Firefox-134, enabling testing on the latest versions +- **Edge :** Updated to Edge-132 for compatibility and stability enhancements. +- **Edge Beta** : Released 133.0.3065.19 for beta testing +- **Chrome :** Upgraded to Chrome-132 to include the newest features and security updates. + +These updates ensure broader coverage for cross-browser testing and improve test stability across the latest browser versions \ No newline at end of file diff --git a/docs/hyperexecute-release-notes-2-7-1.md b/docs/hyperexecute-release-notes-2-7-1.md new file mode 100644 index 000000000..321cf08cb --- /dev/null +++ b/docs/hyperexecute-release-notes-2-7-1.md @@ -0,0 +1,80 @@ +--- +id: hyperexecute-release-notes-2-7-1 +title: Version 2.7.1 +hide_title: false +sidebar_label: Version 2.7.1 +description: Version 2.7.1 +keywords: + - LambdaTest Hyperexecute + - LambdaTest Hyperexecute help + - LambdaTest Hyperexecute documentation + - FAQs +url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-2-7-1/ +site_name: LambdaTest +slug: hyperexecute-release-notes-2-7-1/ +--- + +import NewReleaseTag from '../src/component/newRelease.js'; +import EnhancementTag from '../src/component/enhancementTag'; +import BugFixTag from '../src/component/bugFixTag'; + + +## Artifact Extraction on Job Abortion +- Artifacts will now be extracted even if a job is aborted in the middle of a test. +- This ensures that partial test results and logs are still available for review, improving debugging and post-test analysis. + + +## `afterEachScenario` Flag for Test Cleanup +- Introduced the `afterEachScenario` flag to automate post-test scenario tasks. This flag is useful for cleanup activities such as clearing cookies, resetting databases, or capturing logs. +- Commands or scripts listed under this flag will execute sequentially after each test scenario, ensuring test isolation and consistency. + +```yaml +afterEachScenario: + - echo "Running a script" + - pwsh run.test +``` + +> 📘 Refer to our detailed documentation for [`afterEachScenario`](https://www.lambdatest.com/support/docs/deep-dive-into-hyperexecute-yaml/#aftereachscenario) flag + +## Role-Based Access Control (RBAC) for Projects + +- Implemented RBAC to enhance project security and access management. +- Users can now be assigned specific roles with defined permissions. + +This feature improves security by ensuring that only authorized users can access or modify project settings and resources. + +## UX Enhancements for Performance Testing Jobs +- Improved UI/UX for managing and analyzing performance testing jobs. +- Enhanced navigation and usability for a smoother experience. +- Group-Wise Error View + - Introduced an error grouping feature to help identify and troubleshoot issues efficiently. + - Errors are now categorized for better readability and quicker resolution. +- Toggle Metrics: ms :left_right_arrow: s + - Added the ability to toggle performance metrics between milliseconds (ms) and seconds (s). +- Provides flexibility for analyzing test execution times in preferred units. + +## Browser Version Updates + +- **Edge Beta** : Released 133.3065.31 2.7.1 and 133.3065.39 2.7.2 for beta testing diff --git a/docs/hyperexecute-release-notes.md b/docs/hyperexecute-release-notes.md index 33577eb4f..c3b6b7480 100644 --- a/docs/hyperexecute-release-notes.md +++ b/docs/hyperexecute-release-notes.md @@ -43,11 +43,22 @@ HyperExecute is an AI Powered Test Orchestration Cloud Platform, enabling test a ## HyperExecute Releases +### CLI releases +#### January, 2025 +| Release Number | Release Date | +|----------------|--------------| +| [Version 0.2.249](/support/docs/hyperexecute-cli-release-notes-0-2-249) | January 13, 2025| + ### 2025 releases +#### February, 2025 +| Release Number | Release Date | +|----------------|--------------| +| [Version 2.7.1](support/docs/hyperexecute-release-notes-2-7-1) | February 03, 2025| + #### January, 2025 | Release Number | Release Date | |----------------|--------------| -| [Version 0.2.249](/support/docs/hyperexecute-cli-release-notes-0-2-249) | January 13, 2024| +| [Version 2.7.0](support/docs/hyperexecute-release-notes-2-7-0) | January 27, 2025| ### 2024 releases #### December, 2024 diff --git a/docs/hyperexecute-run-jmeter-tests.md b/docs/hyperexecute-run-jmeter-tests.md index e3b426fe8..052a9e671 100644 --- a/docs/hyperexecute-run-jmeter-tests.md +++ b/docs/hyperexecute-run-jmeter-tests.md @@ -155,10 +155,6 @@ You can analyze the number of requests sent on that particular time. - **Region 1 :** 250 users → 3 machines (lets say it distributed as 84, 83, 83 users per machine). - **Region 2 :** 250 users → 3 machines (lets say it distributed as 84, 83, 83 users per machine). - - **User Allocation per Machine:** Users are evenly distributed among machines to ensure optimal utilization and balanced load: - For example, in Region 1: - Machine 1 = 84 users, Machine 2 = 83 users, Machine 3 = 83 users. - #### Key Takeaways: - **Flexible Overrides :** HyperExecute dynamically adjusts the load distribution and machine allocation based on your specified parameters. - **Optimal Resource Utilization :** It ensures that no machine exceeds the maximum user threshold, maintaining a balanced and efficient test execution. @@ -184,7 +180,7 @@ You can analyze the number of requests sent on that particular time. - **Region 1 :** 3 machines → 250 users per machine. - **Region 2 :** 3 machines → 250 users per machine. - - **User Allocation per Machine :** Each machine in both regions processes **250 users**, resulting in a total of 750 users (250 users × 3 machines) per region. + - **User Allocation per Machine :** Each machine in both regions processes **250 users**, resulting in a total of 750 users (250 users × 3 machines) per region, and overall 1500 users (250 users x 3 machines * 2 regions). #### Key Takeaways: - **Default Behavior :** Without overrides, the user load from the .jmx file is replicated across all configured machines in each region. diff --git a/sidebars.js b/sidebars.js index 536644053..02cb4a727 100644 --- a/sidebars.js +++ b/sidebars.js @@ -825,7 +825,7 @@ module.exports = { id: "hyperexecute-release-notes", }, items: [ - // 2025 releases + // CLI releases { type: "category", collapsed: true, @@ -842,6 +842,30 @@ module.exports = { ] }, + { + type: "category", + collapsed: true, + label: "2025 Releases", + items: [ + { + type: "category", + collapsed: true, + label: "February, 2025", + items: [ + 'hyperexecute-release-notes-2-7-1', + ] + }, + { + type: "category", + collapsed: true, + label: "January, 2025", + items: [ + 'hyperexecute-release-notes-2-7-0', + ] + }, + ] + }, + // 2024 releases { type: "category",