Skip to content

Conversation

hereje
Copy link

@hereje hereje commented Aug 29, 2025

Moving automated tests to Vitest

  • replace jest with vitest
  • remove jest references no longer used

Fixes: #228

Copy link

vercel bot commented Aug 29, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
cashscript Ready Ready Preview Comment Sep 2, 2025 11:05pm

- replace jest with vitest
- remove jest references no longer used
- add vitest configuration file in package
- add vitest configuration file to workspace
- replace jest with vitest
- remove jest references no longer used
- add vitest configuration file in package
- refactor extend functions so that they work
with vitest
- rename jest extensions file as `VitestExtensions.ts`
- add vitest types
- replace jest with vitest
- add vitest configuration file in package
- remove jest configuration file
- remove tests scripts from package.json
- delete tsconfig.test.json config file no longer needed
- add vitest api as global so that import is no required such as
describe, expect, it, etc.
- remove tests scripts from package.json
- delete tsconfig.test.json config file no longer needed
- add vitest api as global so that import is no required such as
describe, expect, it, etc.
- remove tests scripts from package.json
- delete tsconfig.test.json config file no longer needed
- add vitest api as global so that import is no required such as
describe, expect, it, etc.
- replace jest with vitest in examples/testing-suite
- remove jest dependencies
- install vitest dev dependency
- replace jest config files with vitest config files
- pass vitest flags to test execution
@hereje hereje force-pushed the feat/migrate-jest-to-vitest branch from 1d312b7 to 026064d Compare September 2, 2025 17:50
@hereje hereje marked this pull request as ready for review September 2, 2025 17:56
- add globals: true to vitest.config.ts on main
path of workspace
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move moving automated tests to Vitest
1 participant