Create documentation for handling stale elements in k6 #2110
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added guidance on handling stale or dynamic elements in k6 browser tests.
TheComeUpCode
requested review from
AgnesToulet and
mstoykov
and removed request for
a team
Added example code for waiting on DOM changes in k6 tests.
Contributor
|
💻 Deploy preview deleted (Create documentation for handling stale elements in k6). |
ankur22
reviewed
Oct 31, 2025
docs/sources/k6/next/using-k6-browser/recommended-practices/wait-dom-changes.md
Outdated
Show resolved
Hide resolved
…it-dom-changes.md Co-authored-by: Ankur <ankur.agarwal@grafana.com>
ankur22
approved these changes
Oct 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added guidance on handling stale or dynamic elements in k6 browser tests.
What?
Clarifies how to handle asynchronous DOM updates in k6 browser tests. Explains that waiting for navigation alone is insufficient and recommends waiting for specific elements using locator APIs like wait or page.waitForSelector.
Checklist
npm startcommand locally and verified that the changes look good.docs/sources/k6/nextfolder of the documentation.docs/sources/k6/v{most_recent_release}folder of the documentation.docs/sources/k6/nextfolder of the documentation.Related PR(s)/Issue(s)
Closes #2081