Draft Statement of Work - Test reliability lead

[mhdawson]

The test flakiness lead will be expected to:

• lead a test reliability 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

• maintain good test coverage
• reduced number of tests marked as flaky in the status files
• Running node-test-commit on the main branch will pass more often (hopefully always).
• critical mass of contributors/collaborators dedicating time to addressing flaky tests that persists beyond the strategic initiative

[mhdawson]

@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]

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

[joyeecheung]

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]

@joyeecheung updated, thanks for the suggestion.

[mcollina]

I think we should have a more measurable success criteria, such as:

• a list of tests that should be fixed by the individual (mandatory list)
• number of flaky tests fixed (they can decide)

I would structure the agreement as:

• xxx amount at start
• yyy amount at 50% completion
• zzz amount at finish

Alternatively, if the person is a member of the TSC, I would put at:

daily rate of XXX * number of days worked, capped at zzz.

[joyeecheung]

That would be assuming the list of tests doesn't change while this is happening, which is unlikely to be true. Other contributors can always alter the tests as necessary or mark tests as flaky as they see fit, or add more tests while all these are happening, and could use some eyes watching the status of the new tests or otherwise new flakes still come up and we won't be much better off. What we care about is whether the overall situation improves, while the situation isn't always static without the hired individual doing anything.

Also, identifying this list is also non-trivial work, especially when it could be challenging to triage and identify a correct list. It wouldn't be too meaningful if the list contains a lot of false positives, yet eliminating false positives can already be difficult enough.

If we want a quantitative measurement, then I think the rate of a passing node-test-commit CI on the main branch is already enough (which has been around 0% for some time).

[mhdawson]

That would be assuming the list of tests doesn't change while this is happening, which is unlikely to be true.
I agree with that.

I also think we want somebody who will do more than just fix specific tests, helping to improve how we manage and resolve flaky tests though automation and tools is just as important as fixing specific flaky tests.

[Trott]

I've not been privy to this conversation so I might be missing the mark with this comment, but I think it will be more understandable and more professional-sounding if you call it a "test reliability lead" rather than a "test flakiness lead". In a formal/professional document, I wouldn't refer to "flakiness" but instead refer to "reliability" (or "unreliability").

[mhdawson]

@Trott like that suggestion, incorporated.

[mhdawson]

Sent email today to the Foundation executive directory with @mcollina as our CPC rep on CC to ask what might be possible in terms of funding from the OpenJS foundation.

[bnoordhuis]

@mhdawson (or @mcollina) seeing how half a year has passed I'm guessing the answer is 'no' but did you guys ever receive a reply?

[mcollina]

The answer is that there is no money for this right now. We are trying to assess if we can find the funding to make it happen. Specifically, the amount of money that we will receive from HeroDevs. Having said that, most of the funds are spent on keeping the lights up of the Jenkins CI.