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

Research path for migrating tests to node:test #2373

Closed
jsumners-nr opened this issue Jul 17, 2024 · 2 comments
Closed

Research path for migrating tests to node:test #2373

jsumners-nr opened this issue Jul 17, 2024 · 2 comments
Assignees
Labels
points: 5 1-2 weeks

Comments

@jsumners-nr
Copy link
Contributor

We are having show stopping issues with #1962, and various other developments make it less attractive to try and upgrade our tap dependency. As a result, we would like to investigate the feasibility of relying on the node:test package included with Node.js since v18.0.0 (https://nodejs.org/docs/latest/api/test.html#test-runner).

The main question to answer is: can we migrate test suites individually, or do would we need to migrate all of our tests at once?

@workato-integration
Copy link

@newrelic-node-agent-team newrelic-node-agent-team moved this to Triage Needed: Unprioritized Features in Node.js Engineering Board Jul 17, 2024
@jsumners-nr jsumners-nr moved this from Triage Needed: Unprioritized Features to To do: Features here are prioritized for this sprint (jira for remaining tickets) in Node.js Engineering Board Jul 17, 2024
@jsumners-nr jsumners-nr self-assigned this Jul 17, 2024
@jsumners-nr jsumners-nr moved this from To do: Features here are prioritized for this sprint (jira for remaining tickets) to In progress: Issues being worked on in Node.js Engineering Board Jul 17, 2024
@kmudduluru kmudduluru added points: 5 1-2 weeks and removed needs-triage labels Jul 18, 2024
@jsumners-nr
Copy link
Contributor Author

We have a private doc with our findings at https://docs.google.com/document/d/1zXGq7dTtV3TAT7sr-L9DYIx6jp01NUl6mMKX9h4F-AI/edit

The short of it is:

  1. There will be some technical hurdles to overcome when refactoring test suites to utilize node:test, but nothing we can't handle.
  2. The node --test runner can run all of our existing suites and recognize the pass/fail conditions.
  3. We need to update our CI to utilize node --test as the first step.
  4. We need to convert test suites as ongoing tech debt issues.

@github-project-automation github-project-automation bot moved this from In progress: Issues being worked on to Done: Issues recently completed in Node.js Engineering Board Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
points: 5 1-2 weeks
Projects
Archived in project
Development

No branches or pull requests

2 participants