Use Cases

By Mark Gunn

In previous issues we have discussed solid business requirements, a master test plan, and a defect tracking system. The next step in the process, and one which is often overlooked, is to create use cases or test conditions.

Before you can begin to write test cases, you will need to understand how the system is going to be used. The system design documents will reflect how the system will be accessed and how data can be entered. This will be evident in the design or layout of the application. The application users will be able to explain how they intend to use the application. Of course, that has all been worked out and documented by the Business Analyst when the new SOP’s were written that reflect how the new application will impact the work flow. To best reflect how the work flow will affect the application, use cases should be written.

The use case should be a straight forward step by step process for how the users of the application will enter and use information. In its simplest form, they will cover how to Add, Change, and Delete information. Based on the type of application, this will require more detail but these are the basic constructs for a use case.

Without use cases, the test cases may be testing work flows that will never happen or more importantly, overlooking work flows that will happen.

For example; if you didn’t know that an end user will not have all of the information for an application module the first time they begin a new record, then you might construct a test case that was testing a first time completed module. Since a first time completed module initially can not happen, you may overlook in your testing that the system does not allow the user to save a partial record. The use case will cover this scenario and your test cases will accurately reflect these test conditions.

When you have completed your use cases, test cases can now be written so that they will completely test all of the applications requirements, designs and work flows.

Next time….writing good test cases!

Mark Gunn has 25 years experience in the Quality Assurance and FDA validation fields. If you have any questions about these topics, please email Mark at Mark@mgdservices.com