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

Support alternative test runners #670

Open
bjnewman opened this issue May 1, 2023 · 0 comments
Open

Support alternative test runners #670

bjnewman opened this issue May 1, 2023 · 0 comments
Assignees

Comments

@bjnewman
Copy link
Contributor

bjnewman commented May 1, 2023

🚀 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.

@bjnewman bjnewman self-assigned this May 1, 2023
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

No branches or pull requests

1 participant