Roland 2c6b5ae10e test: the component suite's twelve failures, none of them about the component ... The cypress component suite has been failing 12 of 311 for long enough to read as background noise. Every one of them was the test's own fault, and four distinct causes account for all twelve. Dead selectors. `div.ui.label.large`, `div.divider.text`, `.item` and `have.attr 'error'` all named markup the old library rendered. None of them started failing when the library was replaced -- they went on matching nothing, or looking for an attribute no control carries, which is the failure mode that makes a test look broken rather than the code. A tag chip is `.wrolpi-tag`, a Select is a real input whose value can be read, an option carries the ARIA role, and an invalid field says `aria-invalid`. Both directions of that last one are asserted by value: a valid field says `aria-invalid="false"` rather than dropping the attribute, so `not.have.attr` would have passed on absence. Missing context. `useFileWorkerStatus` throws rather than defaulting when its provider is absent, so the channel edit page died on a modal buried three levels down while every other page mounted fine. App.js wraps the whole app in that provider; the mount helper now does too, with the poll slowed to a minute. Unstubbed fetches. The inventory page loads the food catalog from its own endpoint, and the RSS edit form fetched downloaders before its intercept was declared. Both rejected with "Failed to fetch" out of an effect, which Cypress counts as an uncaught application error and fails the running test on -- so three inventory tests and one download test died for a reason unrelated to anything they assert. Assertions reading the wrong thing. `cy.contains('Food Storage')` found the hidden `.inventory-print` copy, since contains takes the deepest match and the print sheet is mounted at all times. And the PUT body arrives as a JSON string, so `req.body.items` was undefined both in the reply the interceptor built and in the assertion waiting on it. The RSS submit test deep-equalled one exact JSON string and broke the moment the video downloader gained eight settings the form fills in by default; the envelope is still matched exactly and the settings are checked for the values the fixture set. It also never waited on its own alias, so an interceptor that never ran would have passed in silence. Separately, the navbar's shrink test read its link count in a bare `.then()` right after the corner finished growing -- before the recalculation that growth triggers had run, so `shrunken` was sometimes already the full count and the assertion came out "expected 10 to be above 10" under load. It now waits for the bar to settle to one row, which is the same signal the test above it asserts, and requires the "More" trigger to exist so it cannot pass having measured a bar that never overflowed. New: two tests for the file browser filter's width, desktop and phone, which is what caught the dead selector behind it. 311 passing, 0 failing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-08-08 18:05:54 -06:00
..
e2e	ui: the last of Semantic UI, in name and in dead CSS	2026-08-08 18:05:54 -06:00
fixtures	Updating cypress tests for new file group routes.	2026-03-21 16:26:08 -06:00
support	test: the component suite's twelve failures, none of them about the component	2026-08-08 18:05:54 -06:00