Practise the standard verbs for diagnosing and reducing Cypress test flakiness.
0 / 5 completed
1 / 5
Fill in: 'We ___ flaky Cypress tests into a quarantine suite so they stop blocking every unrelated pull request.'
We 'move a test' — the standard, simple collocation for relocating an item to another suite. The other options are less idiomatic here.
2 / 5
Fill in: 'A hard-coded wait instead of an assertion can ___ a test passing locally but failing intermittently in CI.'
We say a bad wait will 'cause' intermittent failure — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ retries on known-flaky specs so a single slow network blip doesn't fail the whole CI run.'
We 'enable retries' — the standard, established Cypress collocation for allowing a spec to rerun automatically. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a stable data-testid selector instead of a CSS class so a styling tweak never breaks the test.'
We 'use' a selector — the standard, simple collocation for adopting a reliable targeting strategy. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ flakiness rates per spec in a dashboard so a test that's degrading gets fixed before it's ignored entirely.'
We 'track' a rate — the standard collocation for monitoring a metric over time. The other options aren't idiomatic here.