Repo Testing
Recorded profile Save and insurance export checks: synthetic QA evidence.
General
- Run the smallest relevant test set first, then widen if needed.
- For list pages and report surfaces, verify loaded counts, ordering, and continued loading behavior in the browser.
- Do not assume an API sort change fixed the UI if the frontend can still re-sort or truncate the data.
Frontend
- After frontend changes, run
rtk mise exec -- timeout 30 bin/vite build. - For authorization or role changes, verify with real user flows in the browser when practical.
- For browser crashes, verify the affected page, perform the crashing action, check console errors, and capture a meaningful screenshot checkpoint.
- For deploy-safety fixes, verify stale chunk handling in-browser:
- trigger a lazy-route load failure (or
vite:preloadError) and confirm the app reloads once automatically - confirm subsequent repeated failure shows a reload prompt, not the 404 page
- confirm transient post-deploy
401does not force logout when/api/v1/users/_meis still200
- trigger a lazy-route load failure (or
Ruby
- For Ruby changes, run focused
rspecfiles related to the touched code. - Native image checks require libvips (Ubuntu 24.04:
libvips42t64).spec/initializers/active_storage_image_boundary_spec.rbandscripts/ci/verify_runtime_image.rbcheck the existing EXR boundary, company-logo variants, PNG/JPEG/WebP thumbnails and the Unicode invoice PDF. These native checks verify the existing framework safeguard, not installed package versions or remediation of XML/Chromium findings. - The production runtime verifier also enforces the Debian OpenEXR package floor; passing native image checks alone does not satisfy it.
Mailers
- Run focused mailer specs.
- Verify rendered previews in the browser for representative desktop and mobile widths.