Maurice e3c524dd02 test: give every test case an assertion of its own ...

SonarQube's S2699 flagged 196 test cases as assertion-less. Almost all of
them end on a bare `await screen.findByText(...)`, which does throw when the
text never shows up — the test is real, the analyser just cannot see it.
Spelling the check out keeps the behaviour identical and makes it readable.

Writing them out turned three tests red, each for a good reason:

- FE-COMP-NOTES-008 read the heading out of the loading panel, which renders
  its own copy and swaps the whole node out once the fetch settles. It now
  waits for the loaded state.
- FE-COMP-PHOTOPROVIDERS-014 matched /connected/i, which also matches the
  "Not connected" the badge starts as — the test passed whether or not the
  button did anything. Exact text now.
- FE-FILES-002 compared an empty list against the empty list it already was.
  It seeds a file first, so the 500 has something to leave alone.

JOURNEY-SVC-066 asserted nothing at all behind a "should not throw" comment;
it now says that out loud and checks no journey entry is left orphaned.

2026-08-25 11:02:39 +02:00

..

environment

v3.4.0 (#1540)

2026-07-18 22:13:52 +02:00

helpers

test(client): the coverage that goes with the previous commits

2026-08-23 11:59:12 +02:00

integration

test(client): the coverage that goes with the previous commits

2026-08-23 11:59:12 +02:00

unit

test: give every test case an assertion of its own

2026-08-25 11:02:39 +02:00

setup.ts

fix(client): make the offline core survive a logout and stop clobbering itself

2026-08-23 11:59:12 +02:00