test: mocked e2e coverage for outpatient prioritization and custom forms

[marceloarocha]

Extends the mocked e2e suite to two features that had no coverage at all.

tests/mocked/outpatient/outpatientPrioritization.spec.ts

The PRIMARYCARE patient list (/pacientes-ambulatoriais, src/features/outpatient). 6 tests:

• the default filter payload sent by POST /patient/list on mount (including the hardcoded idSegment: 1), the resolved patient names from POST /names, the observation column showing only the first paragraph, the formatted scheduled date, and the row action opening /prescricao/:id in a new tab;
• the Setores options following the selected Segmento (departments of other segments hidden, a department shared by two segments listed once) and reaching the search payload;
• the secondary filters behind "Ver mais": counted in the badge (segment/department/appointment dates are excluded from the count) and sent as appointment / tags;
• expansion limited to rows carrying marcadores — untagged rows keep only the column spacer — plus the expand-all/collapse-all header toggle;
• the client-side search box filtering by name and by nº atendimento, ignoring inputs of 3 characters or fewer, and never issuing a new request;
• a failing POST /patient/list reporting the error and leaving the empty state.

tests/mocked/customForms/customForms.spec.ts

Evolution forms (/configuracoes/forms-personalizados, src/features/memory/CustomForms). 9 tests:

• the list counting groups and questions per form, the active tag and the name sort;
• editing a form → PUT /memory/custom-forms/:id with the complete record, success notification and navigation back to the list;
• changing a question away from a selection type clearing its options in the saved payload;
• required-field validation (name, group, question id and label) blocking the save, with the header/tab error markers;
• the unique-question-id rule flagging both duplicates ("ID duplicado"), spaces stripped from ids, and the save going through once fixed;
• "Duplicar" navigating to new?copyFrom=<key>, prefilling "Cópia de …" and saving as a new record (PUT /memory/custom-forms, no id in the path);
• the JSON import/export buttons hidden without MAINTAINER, a pasted JSON replacing the form under edit (still saved under the record's own id), and an invalid JSON rejected without touching the form.

Notes

• No production code changed; only new specs plus the folder list in the CLAUDE.md test tree.
• Both suites run under the existing make e2e-mock / e2e-mock.yml workflow. Verified locally with --repeat-each=2: 30/30 green.
• Found while writing the validation test (not fixed here, out of scope for a test-only PR): in CustomFormEditorPage/FormBody, the "Verifique os campos obrigatórios antes de salvar." notification and the automatic jump to the first failing group never fire on the first failed save — the effect depends only on submitCount, so it reads Formik's errors one render too early and bails out; it works from the second attempt on. Adding errors to the effect deps would fix it. The tests assert the field-level errors and the absence of the save request instead, so they stay valid either way.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

🤖 Generated with Claude Code

https://claude.ai/code/session_01RQpzfg94gWWra1P8gmibhv

---

Generated by Claude Code

[amazon-q-developer]

This PR successfully adds comprehensive test coverage for two previously untested features: outpatient prioritization and custom forms. The mocked E2E test suite now includes 15 new test cases (6 for outpatient prioritization, 9 for custom forms) that cover key workflows including filtering, validation, CRUD operations, and error handling.

The tests are well-structured, follow repository patterns, and appropriately use fictitious test data as required by the project guidelines. All changes are test-only additions with no production code modifications, making this a low-risk enhancement to the test suite.

The documentation update to CLAUDE.md correctly reflects the new test directory structure. Ready to merge.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.