fix(e2e): two case assertions that could not pass however well the product worked

[rubenvdlinde]

Two e2e assertions in the case suite could not pass however well the product worked. Both are test defects. Both were measured before they were changed, and both were watched failing and then passing.

The Tags sidebar Save button was never clickable

case-identity.spec.ts picked a tag, confirmed the field, and then clicked the widget's header Save. There is no second step to click. CnObjectDataWidget.commitEdit stages the value and then awaits its own save(), so a click-to-edit confirm writes in one step. The header Save is v-if="isDirty" :disabled="saving", which means it exists only while the write is in flight and is disabled for every millisecond of that. Playwright resolved it, spent the whole budget on "element is not enabled", and then reported it detached, which reads exactly like a broken feature.

The CI trace of the failing run settles it: one PUT /apps/openregister/api/objects/dossiq/case/<id> with {"tags":["spoed"]}, status 200, response body carrying the tag, sent fifteen seconds before the click that timed out. The tag was saved. The test failed on a step the widget does not have.

The click is replaced by an assertion rather than deleted: the widget must be left with nothing staged. A revert to a two-step save leaves a Save button standing there and reddens this, which is the signal a bare deletion would have thrown away.

Opening the timeline is itself an audited event

case-timeline.spec.ts asserted that the newest audit row says update. OpenRegister logs a read on every page load, so by the time the test can look at the list the newest row is the read its own navigation just made. CI reported precisely that: Sep 9, 2026, 07:34 AM / admin / read.

The reads stay in the tab. An inzage-log is what a zaaksysteem owes the person the case is about, and filtering them out at the source would delete the record that answers "who has seen my dossier". The tab already offers the Action filter for narrowing, and the third test in this file covers it.

So the assertion changes instead. It now reads the order of the writes within the list: the update this spec makes after the create has to sit above it. That is the same defect the original guarded, openregister#3540's bottom-up ordering, and the new form still catches it.

Watched failing, watched passing

assertion	before	after
tags: panel.getByRole('button', { name: /^(Save|Opslaan)$/ }).click()	red, element is not enabled then detached, reproduced locally	removed; toHaveCount(0) green
timeline: expect(updateAt).toBeLessThan(createAt)	red on a pre-#3540 instance with "the create sits above the update, so the trail is bottom-up"	green once the rows arrive newest-first

The timeline assertion was mutation checked against the real defect rather than a simulated one. The dev instance this was measured on still runs an openregister that predates #3540 and ignores _sort[created]=DESC, so it serves the trail oldest-first, and the new assertion reddens on it naming the inversion. Feeding the same page a newest-first payload turns it green. Restored from a byte copy afterwards and diffed.

Not in this pull request

The third failure in this batch, the case-type folder button, is a library bound and not a dossiq one. CnFolderSidebar in source: "field" mode built its folders from the loaded page, so a category whose rows sit past row 20 has no folder at all. Measured on a 32-row instance: page one held zero categorised rows, so the pane rendered no folders while two categories existed in the set. ConductionNL/nextcloud-vue#1036 fixes it by reading the facet instead, and the platform already emits a complete category bucket list under _facets=extend. It merged this morning and is not published yet, so dossiq clears that failure with a dependency bump once it is.

[github-actions]

Quality Report — ConductionNL/dossiq @ 0d8c062

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
check-vue3-compile		✅
test-l10n		✅
format		❌
check-schema-l10n		✅
check-l10n-js		✅
composer			✅	✅ 106/106
npm			✅	✅ 549/549
app:check-code	⏭️
info.xml	✅
REUSE	❌
PHPUnit					❌
Newman					⏭️
Playwright					❌
Hydra gates					❌

---

Quality workflow — 2026-09-09 08:55 UTC

Download the full PDF report from the workflow artifacts.

[github-actions]

Quality Report — ConductionNL/dossiq @ 3613bd8

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
check-vue3-compile		✅
test-l10n		✅
format		✅
check-schema-l10n		✅
check-l10n-js		✅
composer			✅	✅ 106/106
npm			✅	✅ 549/549
app:check-code	⏭️
info.xml	✅
REUSE	❌
PHPUnit					✅
Newman					⏭️
Playwright					❌
Hydra gates					✅

---

Quality workflow — 2026-09-09 09:25 UTC

Download the full PDF report from the workflow artifacts.