Number: 69
Testing Efficiency:
Efficiency relates to speed, relates to saving time, relates to optimising things, but of these three things, the key area to make progress is in optimisations.
A focus on speed or time, as a primary objective, may sacrifice quality, whereas a focus on optimisation still actually means ensuring that you’re covering what you should be covering, and when you should be covering it.
This is where a focus on the current context of what is being tested is a way to better ensure that what you’re covering what is relevant to the area under test, too. This relevance is where people are able to filter down from testing everything to filtering (at least initially) just what applies to that area.
A user may still go back (and say prior to signing off or releasing) and then choose to cover more broadly other areas outside of the AUT, in order to identify any additional regressions, or the likes, but it is these other areas where the risk is lower, as the probability of regressions in these other areas is likely lower too.
In addition to the above, efficiencies can also be achieved through process improvements, where something is often not yet found to be in the right state for testing, or some other patterns of issues exist, then by putting in reformed or new processes in those areas better ensures that when the testing is performed, it is more likely to go more smoothly and efficiently too.