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

spike: Benchmark test audit #2115

Open
mrickard opened this issue Apr 2, 2024 · 1 comment
Open

spike: Benchmark test audit #2115

mrickard opened this issue Apr 2, 2024 · 1 comment
Labels
points: 3 A few days

Comments

@mrickard
Copy link
Member

mrickard commented Apr 2, 2024

Spike to determine which tests are being run:

  • Which tests pass
  • Which tests fail
  • Which tests should be kept
  • Which failing tests should be fixed
  • Which tests should be removed
  • Which new tests should be added

Acceptance criteria:
At minimum, this spike should result in lists of

  • which failing tests to fix
  • which failing tests to remove
    and optionally
  • which additional tests are needed

If some successfully completing tests are unnecessary, we can list these for removal as well.

Related to #2114

@workato-integration
Copy link

@newrelic-node-agent-team newrelic-node-agent-team added this to Triage Needed: Unprioritized Features in Node.js Engineering Board Apr 2, 2024
@kmudduluru kmudduluru added points: 3 A few days and removed needs-triage labels Apr 9, 2024
@kmudduluru kmudduluru moved this from Triage Needed: Unprioritized Features to To do: Features here are prioritized for this sprint in Node.js Engineering Board Apr 30, 2024
@kmudduluru kmudduluru moved this from To do: Features here are prioritized for this sprint (jira for remaining tickets) to Triage Needed: Unprioritized Features in Node.js Engineering Board May 16, 2024
@kmudduluru kmudduluru 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 May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
points: 3 A few days
Projects
Node.js Engineering Board
  
To do: Features here are prioritized ...
Development

No branches or pull requests

2 participants