Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consider moving automated tests to a Jest-alternative #228

Open
mr-zwets opened this issue Oct 28, 2024 · 0 comments · May be fixed by #233
Open

consider moving automated tests to a Jest-alternative #228

mr-zwets opened this issue Oct 28, 2024 · 0 comments · May be fixed by #233

Comments

@mr-zwets
Copy link
Member

Jest isn't the fastest testing framework and we have quite a lot of tests for CahsScript.

Jest also has bad ESM support, so our testing command looks like this

"test": "NODE_OPTIONS='--experimental-vm-modules --no-warnings' jest"

We also still have some .cjs files because of it in the /jest folder

Jest also has a highfootprint, it does have a lot of ecosystem integration but I don't think we use those.

Vitest or AVA or the Deno built-in testing suite all have similar syntax to Jest so should be easy to migrate over to.

CashScript would still have Jest as a DevDependency because of the jestExtensions functionality for the debug tooling...
So the main benefits would be in removed complexity & faster tests

@mr-zwets mr-zwets linked a pull request Nov 5, 2024 that will close this issue
7 tasks
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 a pull request may close this issue.

1 participant