diff --git a/docs/kaneai-healing-and-dynamic-test.md b/docs/kaneai-healing-and-dynamic-test.md index 98e4478ad..b17f3049c 100644 --- a/docs/kaneai-healing-and-dynamic-test.md +++ b/docs/kaneai-healing-and-dynamic-test.md @@ -184,6 +184,10 @@ See [KaneAI Test Runs](/support/docs/kaneai-hyperexecute-test-run-execution/#adv When Adaptive Heal or Dynamic Test produces a new version and auto-approve is off, the version appears in the test case's **Version History** marked as a draft, attributed to the strategy that produced it rather than to the person who started the run. +:::note One test case, one draft +A test run can include the same test case under several configurations, such as more than one Chrome version or more than one operating system. It still produces a single draft, because it is one test case. +::: + From there you can read the proposed steps in full, compare them against the current version, and then **Approve** or **Decline**. - **Approve** makes it the current version and regenerates the exported code for it. @@ -201,15 +205,6 @@ A run can be configured in ways that put it outside the scope of Adaptive Heal a Adaptive Heal and Dynamic Test apply to a test case only when it uses New Experience **and** its browser configuration is Chrome. A test case on any other browser, or one not using New Experience, replays its recorded steps and stops at the first step that fails. -### Runs that span several versions -*** - -A test run can be configured across several browser or operating system versions, which produces one test instance per combination. - -**Only the first test instance picked up for execution is eligible.** The remaining instances in that run replay their recorded steps and are not repaired or re-authored. Running a single test case across several Chrome versions or several operating system versions is not supported for these strategies. - -If you need every combination covered, run each version as its own test run. - ### Other boundaries *** diff --git a/static/docs/kaneai-healing-and-dynamic-test.md b/static/docs/kaneai-healing-and-dynamic-test.md index c3eaa4650..47ec2cfb5 100644 --- a/static/docs/kaneai-healing-and-dynamic-test.md +++ b/static/docs/kaneai-healing-and-dynamic-test.md @@ -113,6 +113,9 @@ See [KaneAI Test Runs](/support/docs/kaneai-hyperexecute-test-run-execution/#adv When Adaptive Heal or Dynamic Test produces a new version and auto-approve is off, the version appears in the test case's **Version History** marked as a draft, attributed to the strategy that produced it rather than to the person who started the run. +**One test case, one draft** +A test run can include the same test case under several configurations, such as more than one Chrome version or more than one operating system. It still produces a single draft, because it is one test case. + From there you can read the proposed steps in full, compare them against the current version, and then **Approve** or **Decline**. - **Approve** makes it the current version and regenerates the exported code for it. @@ -128,14 +131,6 @@ A run can be configured in ways that put it outside the scope of Adaptive Heal a Adaptive Heal and Dynamic Test apply to a test case only when it uses New Experience **and** its browser configuration is Chrome. A test case on any other browser, or one not using New Experience, replays its recorded steps and stops at the first step that fails. -### Runs that span several versions - -A test run can be configured across several browser or operating system versions, which produces one test instance per combination. - -**Only the first test instance picked up for execution is eligible.** The remaining instances in that run replay their recorded steps and are not repaired or re-authored. Running a single test case across several Chrome versions or several operating system versions is not supported for these strategies. - -If you need every combination covered, run each version as its own test run. - ### Other boundaries - Only one strategy can be active at a time. Selecting one clears the others.