From 03bd57abe52840170a0a9991539bbd4c6601640e Mon Sep 17 00:00:00 2001 From: anubhavsinghmaar Date: Thu, 10 Sep 2026 19:31:34 +0530 Subject: [PATCH] docs(kaneai): correct what several configurations do to Adaptive Heal and Dynamic Test The page said only the first test instance picked up for execution is eligible, that the rest replay their recorded steps without being repaired, and that a test case across several Chrome or operating system versions is not supported. That is not the behaviour, and it sent a reader to the wrong conclusion twice: that most of their instances would be skipped, and that they should split a run to get coverage. What actually happens concerns the draft, not eligibility. A test run can include the same test case under several configurations, and it produces a single draft, because it is one test case. The claim is removed from When these strategies do not apply, where it did not belong, since this is not a case of the strategies failing to apply. The correct behaviour is stated as a note in Reviewing a change, beside the version it is about. Co-Authored-By: Claude Opus 4.8 --- docs/kaneai-healing-and-dynamic-test.md | 13 ++++--------- static/docs/kaneai-healing-and-dynamic-test.md | 11 +++-------- 2 files changed, 7 insertions(+), 17 deletions(-) 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.