Skip to content

fix: expect.getState().testPath always returns correct path #11299

fix: expect.getState().testPath always returns correct path

fix: expect.getState().testPath always returns correct path #11299

Triggered via pull request September 11, 2024 18:20
Status Failure
Total duration 13m 54s
Artifacts

ci.yml

on: pull_request
Diff: node-latest, ubuntu-latest
6s
Diff: node-latest, ubuntu-latest
Lint: node-latest, ubuntu-latest
2m 30s
Lint: node-latest, ubuntu-latest
Matrix: test-browser
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 errors
specs/runner.test.ts > running browser tests > tests are actually running: test/browser/specs/runner.test.ts#L27
AssertionError: expected [ { …(6) }, { …(6) }, { …(6) }, …(13) ] to have a length of 17 but got 16 - Expected + Received - 17 + 16 ❯ specs/runner.test.ts:27:25
Browser: firefox, windows-latest
Process completed with exit code 1.
test/basic.test.tsx > Link changes the state when hovered: examples/workspace/packages/client/test/basic.test.tsx#L18
Error: expect(element).toHaveAccessibleName() Expected element to have accessible name: Link is hovered Received: Link is normal ❯ test/basic.test.tsx:18:16
Build&Test: node-20, windows-latest
Process completed with exit code 1.