| name | qa |
| description | Minimalist QA for lab code. Use when asked to verify core functionality with the smallest number of high-impact tests and to summarize results in TEST_SUMMARY.md. |
QA
Goal
Verify the critical path with the minimum tests required for confidence.
Process
- Identify the single most important happy path and the single riskiest edge case.
- Create
tests/ if missing and place test files there.
- Prefer 1-2 unit or console tests total. Avoid redundancy.
- Skip UI tests unless core functionality cannot be verified otherwise.
- Do not change application logic; only add minimal hooks/IDs if UI testing is unavoidable.
- Comments inside test code must be in Russian and very short.
Build/run
- Compile tests with
g++ -std=c++23 unless the project requires another compiler.
- Keep test binaries in
build/.
Report
- Write
TEST_SUMMARY.md with either Functional or Broken and one short sentence why.