A common grievance amongst testers is the lack of requirements, especially quality requirements that are conducive to crafting applicable tests. Unfortunately, there are no solutions, automated or otherwise, for producing good functional requirements.
If requirements are complete and test cases have been created to cover them, in most cases you’ll gain visibility around the impact of failing test cases.
But you also need a way to test non-functional requirements to understand what happens inside the system as the code is exercised.
- Is the application secure?
- Does the application perform reliably?
- Where is the business risk?
You can answer these questions by implementing a tool to capture code coverage, collect metrics and correlate them with test results to make informed decisions about when to release and the impact of change.