You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect that only Test A is executed, but in fact Test D is also run (demonstrated by the failing verification):
TAP version 13
ok 1 Module A > Test A
not ok 2 Module C > Module D > Test D
---
message: failed, expected argument to be truthy, was: 0
severity: failed
actual : 0
expected: true
stack: |
at Object.<anonymous> (/SNIP/demo.js:22:11)
...
1..2
# pass 1
# skip 0
# todo 0
# fail 1
I verified that this does not reproduce in release 2.13.0, introduced in 2.14.0, and could very well be related to #1527.
The text was updated successfully, but these errors were encountered:
… also executed
This fixes a regression introduced in 2.14.0, restoring the behaviour from 2.13 and earlier.
When `QUnit.module.only()` is used, and there is a later sibling module (implicitly disabled
by the "only" filter), with the later module having a nested module inside it, then since
2.14 that nested module would execute as if it was part of the "only" filter.
Fixes#1610.
Using latest QUnit 2.15.0 via CLI.
Repro:
I expect that only
Test A
is executed, but in factTest D
is also run (demonstrated by the failing verification):I verified that this does not reproduce in release 2.13.0, introduced in 2.14.0, and could very well be related to #1527.
The text was updated successfully, but these errors were encountered: