docs: Document SKIPPED test result status and context matching behavior #114
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.
Adds documentation for the SKIPPED result status that was previously undocumented. Updates the intro to clarify that tests can result in PASS, FAIL, or SKIPPED (not just PASS/FAIL). Adds a new section in the contexts documentation explaining when tests are skipped due to platform or browser mismatches, including example JSON output. This documentation aligns with the bug fix in PR #368 that corrected tests to show SKIPPED instead of false PASS when all contexts are skipped.
Open this suggestion in the Promptless dashboard
Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.
If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)