Doing scrutiny with below points may help to maintain your unit test suite to make more sense
Developer experience
- How easy it is to use the test suite for a developer in a busy day ?
- Is your CI is good enough to execute your tests frequent enough ?
Test failures
- Break a code unit and find which tests are failing. it should expose week points
Test case descriptions and error messages
- how accurate are the Error messages on failure of test ? Are you able to find out what exactly broken just by looking at the message ?
- How easy it is for you to understand what the code unit is responsible for just by looking at log of test suite execution ?
Test suite performance
- Are there any tests taking unreasonable or significant amount of time ?
- Consider skipping such tests and find the root cause of low performance of that test. This should help you to know the unknowns on which the implementation is relaying on.
Top comments (0)