Identify and Prioritize Test Cases Based on Risk and Critical Functionality
Why test?
· To refine prototypes and solutions:
§ Testing informs the next iterations of prototypes. Sometimes this means going back to the drawing board.
· To learn more about your user:
§ Testing is another opportunity to build empathy through observation and engagement — it often yields unexpected insights.
· To refine your POV:
§ Sometimes testing reveals that not only did you not get the solution right, but also that you failed to frame the problem correctly.
How to test?
· Show don’t tell:
§ Put your prototype in the user’s hands – or your user within an experience. And don’t explain everything (yet).
§ Let your tester interpret the prototype.
§ Watch how they use (and misuse!) what you have given them, and how they handle and interact with it; then listen to what they say about it, and the questions they have.
· Create Experiences:
§ Create your prototypes and test them in a way that feels like an experience that your user is reacting to, rather than an explanation that your user is evaluating.
· Ask users to compare:
§ Bringing multiple prototypes to the field to test gives users a basis for comparison, and comparisons often reveal latent needs.
Here are a couple of examples of case studies that illustrate the process of identifying high-risk areas or critical functionalities within a prototype and how these priorities influence the testing strategy:
- E-commerce Website Redesign: Imagine a scenario where an e-commerce company is planning to launch a redesigned version of their website to improve user experience and increase sales. During the prototyping phase, the development team identifies several critical functionalities that could significantly impact user satisfaction and conversion rates, such as the checkout process, search functionality, and product pages.To prioritize testing efforts, the team conducts a risk assessment to determine the potential impact and likelihood of failure for each critical functionality. They identify the checkout process as the highest-risk area due to its complexity and direct impact on revenue generation. As a result, the testing strategy focuses heavily on comprehensive testing of the checkout process, including usability testing, functional testing, and performance testing under various scenarios (e.g., high traffic volumes, different payment methods).In contrast, less critical functionalities, such as user account management or product filtering options, may receive less extensive testing coverage, allowing resources to be allocated more efficiently based on risk.
- Medical Device Prototype Testing: In another scenario, a medical device manufacturer is developing a prototype for a new diagnostic tool intended for use in hospitals. The prototype includes critical functionalities such as patient data input, real-time monitoring, and diagnostic result display. During the prototype development phase, the engineering team collaborates closely with healthcare professionals to identify high-risk areas that could impact patient safety and diagnostic accuracy. Through this collaboration, they prioritize testing efforts on functionalities related to accurate data capture, reliable sensor readings, and secure data transmission. Additionally, regulatory requirements for medical devices play a significant role in determining testing priorities. The team ensures that testing activities align with regulatory standards and guidelines for medical device development, focusing on areas with the highest regulatory scrutiny and potential impact on patient safety. By prioritizing testing efforts based on the critical functionalities and associated risks, the development team can develop a comprehensive testing strategy that effectively addresses potential issues and ensures the safety and reliability of the prototype before market release.
Now, view the following video to get a better understanding on ideation techniques