Skip to content

docs(kaneai): correct what several configurations do to Adaptive Heal and Dynamic Test #3516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
anubhavsinghmaar wants to merge 1 commit into
base: stage
Choose a base branch
from
Open

docs(kaneai): correct what several configurations do to Adaptive Heal and Dynamic Test #3516

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 4 additions & 9 deletions docs/kaneai-healing-and-dynamic-test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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
***

Expand Down
11 changes: 3 additions & 8 deletions static/docs/kaneai-healing-and-dynamic-test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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.
Expand Down