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 multiple test runners as part of HHv3 #4925

Closed
4 tasks done
kanej opened this issue Feb 22, 2024 · 0 comments
Closed
4 tasks done

Support multiple test runners as part of HHv3 #4925

kanej opened this issue Feb 22, 2024 · 0 comments
Assignees
Labels
status:needs-decision We need to make a decision about this
Milestone

Comments

@kanej
Copy link
Member

kanej commented Feb 22, 2024

After HH + EDR, fork main and split out the mocha test runner.
We want to add an abstraction that will allow plugins to swap in an alternative test runner.
A minimal alternative runner should be built based on the in-built node test runner (available since v20).
A plugin that encapsulates the current mocha test runner should also be created.

It is not a goal to resolve which test runner should be default in v3. It is not a goal to determine which assertion libraries or network helpers should be used.

TODO

  • Pull together info on the most popular test runners, to aid our decision of default test runner
  • Create a test runner abstraction that is pluggable
  • Move the exiting mocha runner into that abstraction
  • Add a simple test runner based on the most popular test runner
@kanej kanej added this to the vnext milestone Feb 22, 2024
@github-actions github-actions bot added the status:ready This issue is ready to be worked on label Feb 22, 2024
@ChristopherDedominici ChristopherDedominici linked a pull request Feb 27, 2024 that will close this issue
@ChristopherDedominici ChristopherDedominici added status:needs-decision We need to make a decision about this and removed status:ready This issue is ready to be worked on labels Apr 8, 2024
@kanej kanej closed this as completed May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs-decision We need to make a decision about this
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants