Repository navigation
Tests after closed describe.skip no longer marked skipped - #284
Merged
Merged
Conversation
|
🌀 Tests overview by Testomatio Found 301 mocha tests in 27 files ✔️ Added 2 tests+ jest parser: sibling after skipped suite: should not leak a skipped suite onto sibling tests declared after it
+ mocha parser: sibling after skipped suite: should not leak a skipped suite onto sibling tests declared after it📎 List all suites (26)
|
DavertMik
approved these changes
Oct 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Tests declared after a closed describe.skip were falsely marked skipped and placed in the wrong suite. Now only suites still enclosing the test line count (same as playwright). Fixed for mocha, jest, jasmine, qunit, nightwatch + regression tests.
#283