Last week has been pretty busy with strategy meetings and customer interactions. As usual all the customer interactions offer something to learn, so was this particular interaction.
One of the customers asked me if our testing team can identify the business risks for the end-user, based on the progress of test execution. It is not an easy question to answer. The challenge in user based testing is to link the testing progress with the functionality coverage and to figure out the dependencies between different functionalities. The bigger challenge is in the non-functional aspects.
Many times, the application or the product will have to interoperate with others. Identifying the risks in this context becomes even harder. Performing an end-to-end integration testing will be a challenge in the intermediate releases. The issue is not easy even in the standalone environment. Predicting relationships between two requirements without a view into the code is a challenging task.
One needs to leverage a set of factors to be able to identify the business risks based on the progress of user based testing:
– History of different releases is the most important factor
– Looking into the code coverage also helps
In this context, a good tester must employ the proven testing optimization techniques. There may be a way to feed in the findings from exploratory testing as well.
Do let me know your thoughts on some of the other ways you have effectively used to identify the business risks for the end-user.