Skip to content

Move moving automated tests to Vitest #228

Open
@mr-zwets

Description

@mr-zwets
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

Activity

linked a pull request that will close this issueswitch testing from Jest to Vitest [DRAFT] #233on Nov 5, 2024
added this to the v0.11.1 milestone on Jan 15, 2025
changed the title [-]consider moving automated tests to a Jest-alternative[/-] [+]Move moving automated tests to Vitest[/+] on Jan 29, 2025
modified the milestones: v0.11.1, v0.11.2, v0.12.0 on Jun 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    refactorInternal refactoringtestsRelated to automated tests

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      Participants

      @rkalis@mr-zwets

      Issue actions

        Move moving automated tests to Vitest · Issue #228 · CashScript/cashscript