|
| 1 | +--- |
| 2 | +id: hyperexecute-release-notes-2-8-1 |
| 3 | +title: Version 2.8.1 |
| 4 | +hide_title: false |
| 5 | +sidebar_label: Version 2.8.1 |
| 6 | +description: Version 2.8.1 |
| 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-2-8-1/ |
| 13 | +site_name: LambdaTest |
| 14 | +slug: hyperexecute-release-notes-2-8-1/ |
| 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 | + |
| 21 | +<script type="application/ld+json" |
| 22 | + dangerouslySetInnerHTML={{ __html: JSON.stringify({ |
| 23 | + "@context": "https://schema.org", |
| 24 | + "@type": "BreadcrumbList", |
| 25 | + "itemListElement": [{ |
| 26 | + "@type": "ListItem", |
| 27 | + "position": 1, |
| 28 | + "name": "Home", |
| 29 | + "item": "https://www.lambdatest.com" |
| 30 | + },{ |
| 31 | + "@type": "ListItem", |
| 32 | + "position": 2, |
| 33 | + "name": "Support", |
| 34 | + "item": "https://www.lambdatest.com/support/docs/" |
| 35 | + },{ |
| 36 | + "@type": "ListItem", |
| 37 | + "position": 3, |
| 38 | + "name": "Version", |
| 39 | + "item": "https://www.lambdatest.com/support/docs/hyperexecute-release-notes-2-8-1/" |
| 40 | + }] |
| 41 | + }) |
| 42 | + }} |
| 43 | +></script> |
| 44 | +## Enhanced `failFast` at the Scenario Level |
| 45 | +We have made am enhancement to our test configuration: the ability to use [`failFast`](http://lambdatest.com/support/docs/deep-dive-into-hyperexecute-yaml/#failfast) at the scenario level! |
| 46 | + |
| 47 | +Previously, `failFast` could only be applied at the test level. Now, with this update, you can configure `failFast` to stop further scenario execution after a specified number of failed scenarios, providing more granular control over your testing process. |
| 48 | + |
| 49 | +### Key Features: |
| 50 | +- **Granular Control:** Apply failFast to individual scenarios instead of the entire test suite. |
| 51 | +- **Easy Configuration:** Simply set the level to scenario in the YAML configuration. |
| 52 | +- **Max Test Failures:** Control the maximum number of allowed test failures at the scenario level. |
| 53 | + |
| 54 | +Example YAML Configuration: |
| 55 | + |
| 56 | +```yaml |
| 57 | +failFast: |
| 58 | + maxNumberOfTests: 2 |
| 59 | + level: scenario |
| 60 | +``` |
| 61 | +
|
| 62 | +> **Note:** You can use `failFast` either at the test level or scenario level, but not both simultaneously. |
| 63 | + |
| 64 | +This enhancement brings more flexibility to your testing setup, helping you better manage the execution flow and quickly pinpoint issues. |
0 commit comments