Testing Helm

Test the behavior affected by the change. Types, source tests, database execution and browser flows establish different things and complement one another.

Choose the layer

Use the test inventory to map a feature to its meaningful cases. The runner guide explains package commands; evidence boundaries explains what a pass cannot establish.

Financial flow cases

Recording needs correct amount, currency, date and ownership. Corrections need a traceable result. Imports need review before consent, continuation after interruption, and eligible undo. An uncertain money save needs recovery without duplication.

First-use and privacy cases

Verify account creation separately from dated balance confirmation. Unknown and zero have different meaning. Test signup, fresh owned reads, route guidance, skip/replay and existing-user orientation.

Exercise sign-out, account change, browser Back and delayed responses with actual mounted private components. Include dialogs and portals.

Safe test data

Use an authorized development environment and disposable synthetic users. Keep credentials and private financial data out of test output. Clean only the exact fixtures you created and verify the intended scope.

Documentation cases

Validate stable routes and references, then review compiled pages, search, keyboard navigation and mobile themes. A page count alone does not prove a guide teaches a useful task.