Test suite inventory by level and runtime
Before anyone argues about the test pyramid, it helps to know the shape you actually have. Counting tests by level, measuring how long each level takes and noting which folders have none turns a vague feeling that the suite is slow or thin into numbers a team can plan against.
First tasks
- Run the full suite once with timing output switched on and save the report
- Tag each test folder as unit, integration or end-to-end in a spreadsheet
- List production modules that no test file imports
- Commit the inventory as a short document in the docs folder