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

Draft Statement of Work - Test flakiness lead #1629

Open
mhdawson opened this issue Oct 2, 2024 · 4 comments
Open

Draft Statement of Work - Test flakiness lead #1629

mhdawson opened this issue Oct 2, 2024 · 4 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 2, 2024

The test flakiness lead will be expected to:

  • lead a test flakiness strategic initiative, rallying and supporting contributors who work to reduce flaky tests. This might include running regular test team meetings, documentation, tools, or whatever strategy works to achieve more than they can do on their own
  • build tools and improve automation that allows the project to effectively manage flaky tests to reduce their impact on the CI
  • Investigate and fix existing tests being marked as flaky in the status files

Duration

  • 6 months

Success looks like

  • reduced number of tests marked as flaky in the status files
  • more CI runs that pass on the first run
  • critical mass of contributors/collaborators dedicating time to addressing flaky tests that persists beyond the strategic initiative
@mhdawson
Copy link
Member Author

mhdawson commented Oct 2, 2024

@nodejs/tsc as discussed in the TSC meeting today a first cut at what a statement of work for a test flakiness lead might look like.

@mhdawson
Copy link
Member Author

mhdawson commented Oct 7, 2024

Adding to agenda so that we review/get feedback in a future meeting.

@joyeecheung
Copy link
Member

joyeecheung commented Oct 7, 2024

I think we should explicitly add:

Investigate and fix existing tests being marked as flaky in the status files

Success looks like
...reduced number of tests marked as flaky in the status files

Otherwise this might just optimize towards marking all the tests as flaky and let them rot in the status files, which isn't ideal.

@mhdawson
Copy link
Member Author

mhdawson commented Oct 8, 2024

@joyeecheung updated, thanks for the suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants