feat: automation framework analysis and reusable test scripts

[devin-ai-integration]

Summary

Comprehensive analysis of the existing Cypress/Vitest test automation framework and generation of 57 new reusable E2E test scenarios — all built entirely on existing support infrastructure with zero new support modules or duplicate selectors.

Deliverables

Part 1 — Framework Analysis:

• FRAMEWORK_ANALYSIS.md: Documents all 5 Cypress support modules, 24+ exported selectors, 15 custom commands, test data management patterns, design patterns, and gap analysis

Part 2 — New Automation Scripts (5 files, 57 test cases):

• bank-account-management.cy.ts — 13 tests: form validation, update balance/name, multi-account list, API CRUD
• operation-management.cy.ts — 14 tests: form validation (including date default value handling), bank account association, label assignment, update flows, pagination, API CRUD
• label-management.cy.ts — 12 tests: form validation (including minlength), update, multi-label management, API CRUD
• authentication-flows.cy.ts — 10 tests: JWT token storage/clearing, role-based access (admin vs user API), error handling, session persistence
• cross-entity-workflows.cy.ts — 8 tests: full financial workflows (account→operation→label), navigation flows, entity menu navigation, data cleanup ordering

Part 3 — Reusability Report:

• AUTOMATION_REUSABILITY_REPORT.md: Component reuse matrix, page object coverage map, entity/auth coverage tables, standards guide for future script generation

Key Design Decisions

• 100% reuse of existing support modules (commands.ts, entity.ts, account.ts, navbar.ts)
• 0 new support files created — existing infrastructure was sufficient
• All tests follow JHipster patterns: API-seeded data, intercepted responses, session-cached auth, afterEach cleanup
• Previously unused setFieldSelectToLastOfEntity() command now exercised in operation-management tests
• Admin credentials use separate E2E_ADMIN_USERNAME/E2E_ADMIN_PASSWORD env vars to avoid conflicts with regular user credentials
• Date field tests account for OperationFormService.getFormDefaults() pre-populating with currentTime

Review & Testing Checklist for Human

• Review FRAMEWORK_ANALYSIS.md for accuracy against actual codebase
• Verify new test scripts follow existing patterns by comparing with bank-account.cy.ts, operation.cy.ts, label.cy.ts
• Run npx eslint src/test/javascript/cypress/ to confirm lint passes
• Run E2E tests against a running backend: npm run ci:e2e:run (requires backend at localhost:8080)
• Review AUTOMATION_REUSABILITY_REPORT.md standards guide for team adoption

Notes

• All new tests are additive — no existing test files were modified
• Tests requiring a running backend use cy.authenticatedRequest() for API-seeded test data, consistent with existing patterns
• The authentication-flows.cy.ts tests for role-based access require both admin/admin and user/user credentials (default JHipster dev users)
• Admin credentials are read from E2E_ADMIN_USERNAME/E2E_ADMIN_PASSWORD env vars (falling back to admin/admin), separate from regular user credentials

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/0cfbe2c6e70c44b5861c5c9872066b10
Requested by: @bsmitches

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring