🚀 Feature request
Current Behavior
Currently workflow requires users to test using the Jest framework, which until recently has been the best available option for our use case. However, recently several alternatives to Jest have started to gain significant adoption, and as our applications have grown, Jests memory usage and overall performance have become a major friction point. Right now on internal CI servers large apps with hundreds of jest tests regularly require special handling as the memory usage grows, and with restricted memory running unit tests can take several minutes.
Desired Behavior
Add experimental support for at least one alternate test runner, from vitest or swc/jest to explore potential perf improvements and overall compatibility.
Suggested Solution
Add support in workflow.js or a cli flag to change av test to use a non-jest test runner and use it to successfully run unit tests in a workflow app.
Who does this impact? Who is this for?
Workflow users who write unit tests 👀
Describe alternatives you've considered
Could we potentially run our CI builds on more powerful instances? Hahahahaha, no.
Are unit tests even worth writing, shouldn't we just write integration tests? (🤔 Under different circumstances, maybe. For now, just please write some tests)
Additional context
I'm assigning this to myself and gonna get it done soon just adding an issue to keep track of any pre-PR testing or discussion.
🚀 Feature request
Current Behavior
Currently workflow requires users to test using the Jest framework, which until recently has been the best available option for our use case. However, recently several alternatives to Jest have started to gain significant adoption, and as our applications have grown, Jests memory usage and overall performance have become a major friction point. Right now on internal CI servers large apps with hundreds of jest tests regularly require special handling as the memory usage grows, and with restricted memory running unit tests can take several minutes.
Desired Behavior
Add experimental support for at least one alternate test runner, from vitest or swc/jest to explore potential perf improvements and overall compatibility.
Suggested Solution
Add support in workflow.js or a cli flag to change av test to use a non-jest test runner and use it to successfully run unit tests in a workflow app.
Who does this impact? Who is this for?
Workflow users who write unit tests 👀
Describe alternatives you've considered
Could we potentially run our CI builds on more powerful instances? Hahahahaha, no.
Are unit tests even worth writing, shouldn't we just write integration tests? (🤔 Under different circumstances, maybe. For now, just please write some tests)
Additional context
I'm assigning this to myself and gonna get it done soon just adding an issue to keep track of any pre-PR testing or discussion.