Skip to content
build

Vitest Migration #1107

Sign in to view logs

Vitest Migration

Vitest Migration #1107

Triggered via pull request March 4, 2025 13:21
@notaphplovernotaphplover
synchronize #462
chore/migrato-vitest
Status Failure
Total duration 2m 48s
Artifacts –

build.yaml

on: pull_request
Build
2m 37s
Build
Matrix: Test package
Run E2E tests.
0s
Run E2E tests.
Run benchmarks
0s
Run benchmarks
Done
0s
Done
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 warnings
Build
Process completed with exit code 1.
Build: packages/foundation/libraries/reflect-metadata-utils/src/reflectMetadata/utils/updateOwnReflectMetadata.spec.ts#L98
Prefer `vi.mocked()`
Build: packages/foundation/libraries/reflect-metadata-utils/src/reflectMetadata/utils/updateReflectMetadata.spec.ts#L98
Prefer `vi.mocked()`
Build: packages/container/libraries/strongly-typed/src/container.spec.ts#L174
Prefer using `toBe(true)` to test value is `true`
Build: packages/docs/tools/inversify-code-examples/src/examples/bindingToSyntaxApiToProvider.int.spec.ts#L19
Use `expect().resolves` instead
Build: packages/docs/tools/inversify-code-examples/src/examples/bindingToSyntaxApiToProvider.int.spec.ts#L22
Use `expect().resolves` instead
Build: packages/docs/tools/inversify-code-examples/src/examples/containerApiGetAllAsync.int.spec.ts#L7
Use `expect().resolves` instead
Build: packages/docs/tools/inversify-code-examples/src/examples/containerApiGetAllAsyncEnforced.int.spec.ts#L12
Use `expect().resolves` instead
Build: packages/docs/tools/inversify-code-examples/src/examples/containerApiGetAllAsyncEnforced.int.spec.ts#L13
Use `expect().resolves` instead
Build: packages/docs/tools/inversify-code-examples/src/examples/containerApiGetAllNamedAsync.int.spec.ts#L7
Use `expect().resolves` instead
Build: packages/docs/tools/inversify-code-examples/src/examples/containerApiGetAllNamedAsync.int.spec.ts#L8
Use `expect().resolves` instead