Skip to content

test(case): follow the renamed case widgets so development goes green - #4151

Merged
rubenvdlinde merged 1 commit into
developmentfrom
r24/fix-red-base-tests
Oct 22, 2026
Merged

rubenvdlinde merged 1 commit into
developmentfrom
r24/fix-red-base-tests

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

What

Eight vitest specs in pipelinqCaseSurfaces.spec.js and recordPageLibraryWidgets.spec.js fail on development.

Why they failed

The code is right and the tests were stale:

  • Batch 25 (chore: dossiq integration batch 25 #4134) renamed family-plan to goal-plan and case-pipelinq-contact-moments to linked-contact-moments. RenamedLayoutIds rewrites stored layouts to the new ids. The specs still looked up the old ids.
  • Batch 28 (chore: dossiq integration batch 28 #4143) moved the simple case page's planned follow-ups and typed relations into case-related-cases-card, which typedRelatedCasesCard.spec.js covers. case-related-card keeps only the parent case and Plan follow-up. The spec still expected extraSources on it.

Change

  • The specs now use the new ids and the new simple card.
  • Two manifest _notes said these ids would be renamed later. They now say the ids were renamed.

There is no runtime change.

Verified

  • npx vitest run on both files: 60 passed. On development: 8 failed.
  • eslint passes on both files.

AI disclosure: prepared with Claude Code (claude-opus-5-5).

🤖 Generated with Claude Code

Batch 25 renamed family-plan to goal-plan and case-pipelinq-contact-moments
to linked-contact-moments, with RenamedLayoutIds rewriting stored layouts,
and batch 28 moved the planned follow-ups and typed relations of the simple
case page into case-related-cases-card. The code is right; eight specs in
pipelinqCaseSurfaces and recordPageLibraryWidgets still read the old ids and
the old simple card. They follow the new ones now, and two notes that said
the ids would be renamed later say they were.

Assisted-by: ClaudeCode:claude-opus-5-5
@rubenvdlinde
rubenvdlinde merged commit 16e09bf into development Oct 22, 2026
44 of 49 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/dossiq @ 35dd91a

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 ✅
check-debt-ratchet ❌
check-types-e2e ✅
composer ✅ ✅ 109/109
npm ✅ ✅ 658/658
app:check-code ⏭️
info.xml ✅
REUSE ❌
lockfile sync ✅
PHPUnit ❌
Newman ⏭️
Playwright ⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it locally with npx playwright test, or from the Actions tab on a branch with no open pull request into development.
Hydra gates ❌

Quality workflow — 2026-10-22 06:05 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant