Maintain a lightweight model of the application under test to organize and track test coverage.
Keep an intuitive, lightweight model of the application under test. Use it to organize existing tests, identify coverage gaps, and guide where to invest automation effort next.
Build a domain model by surveying:
Record this model in a COVERAGE.md file at the project root or in a docs/ directory.
Survey all existing test files and map each to a domain and feature:
tests/ui/ — map to pages and features.api/{domain}/{endpoint}/ — map to endpoints.For each domain and feature, assess:
Rank gaps by:
Update the coverage model as tests are added or the application changes. Keep it lightweight — a simple table or checklist is better than an elaborate document that falls out of date.