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
Tests that use Vitest's .skipIf (and I presume .runIf) show up failed because "Test result not found.".
To Reproduce
Try for example:
constisDev=truedescribe.skipIf(isDev)("suite 1",()=>{test("skipped if isDev",()=>{expect(true).toBe(true)})})describe("suite 2",()=>{test.skipIf(isDev)("also skipped if isDev",()=>{expect(true).toBe(true)})})
Expected behavior
Tests like this should not automatically err out.
Ideally they should be ignored or included depending on the result of the condition (perhaps assume that a missing test result means that it was skipped?) - or in the worst case perhaps just treat them like skipped tests?
Screenshots
Environment
OS: macOS
VSCode version: 1.67.2 (Universal)
Vitest version: 0.12.6
Vitest plugin version: v0.2.3
The text was updated successfully, but these errors were encountered:
Describe the bug
Tests that use Vitest's .skipIf (and I presume .runIf) show up failed because "Test result not found.".
To Reproduce
Try for example:
Expected behavior
Tests like this should not automatically err out.
Ideally they should be ignored or included depending on the result of the condition (perhaps assume that a missing test result means that it was skipped?) - or in the worst case perhaps just treat them like skipped tests?
Screenshots
Environment
The text was updated successfully, but these errors were encountered: