-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsiderstestingBuilt-in testing supportBuilt-in testing supportverifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: No
- VS Code Version: 8fd821a
- OS Version: macOS 26.0.1
Steps to Reproduce:
- Have a Test Provider that provides two tests A and B.
- Start a test run and mark both tests as passed.
- Start another test run and do:
testRun.enqueued(A); testRun.enqueued(B); testRun.passed(B); testRun.end();
Expected Behaviour: The user can tell from the UI that test A was never completed.
Actual Behaviour:
You'll see how both A and B switch to the "enqueued" icon, and then both switch to the "passed" icon. To the user, this looks like both tests were executed and both tests are green.
The reason for this is that:
- tests that were never finished are switched back to
Unset Unsetresults are ignored in the Icon selection
This is a footgun, because a buggy test extension that forgets executing or recording a test result will produce false negatives. Extensions can work around this by tracking unfinished tests themselves, and marking them as skipped before ending the test run.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsiderstestingBuilt-in testing supportBuilt-in testing supportverifiedVerification succeededVerification succeeded