diff --git a/docs/backlog/jest-cases-the-browser-suite-could-take.md b/docs/backlog/jest-cases-the-browser-suite-could-take.md index e048a091f8..c9e17c4f6e 100644 --- a/docs/backlog/jest-cases-the-browser-suite-could-take.md +++ b/docs/backlog/jest-cases-the-browser-suite-could-take.md @@ -9,8 +9,9 @@ Removing a jest case is only safe when a named e2e case asserts the same behavio assertion. Working through the suites on that rule, the cases that stay divide into a few recurring causes, and most of them are a gap in the browser suite rather than something it cannot reach. -This is the list to work from. It is deliberately not acted on in the same change as the deletions: -each item is an e2e case to write, and the jest cases it releases can then go with it. +This was the list to work from. The items marked **done** below have their browser case and their +jest cases have gone with them; what is left is what is still open, and the reasons it is open are +worth more than the list itself. ## Selectors the browser cannot reach @@ -18,25 +19,30 @@ each item is an e2e case to write, and the jest cases it releases can then go wi browser case cannot select by it. Only one of the elements these jest cases assert through is actually stuck behind that: -- `comments-counter` in `profile.spec.tsx`, asserted in four cases, is +- **done.** `comments-counter` in `profile.spec.tsx` is `