Saturday, May 22, 2010

Common Use Cases to Generate User-Input Test Cases

The most common and underused tool available for gaining good test coverage on your product or application regardless if it's automated or manually done is a checklist. A checklist dictates what process or steps to take when encountering a particular use case similar to how an expert would know what to do given that he had substantial experience over the matter. Thus, it can also be used as an effective way of rapidly transferring knowledge over to other individuals later on. It can also help you prevent from forgetting obvious tests when you are engaged with a very complex test suite.

Here's a checklist of generalized and common input use cases adequate enough to generate your application-specific test checklist that you can later transform into a test case, test plan or test suite.

1. Check for inputs with invalid data type
2. Check for inputs with special characters / multi-byte characters
3. Check for inputs with null values
4. Check for inputs that could potentially run front-end and back-end scripts
5. Check for inputs that are outside the maximum-length
6. Check for duplicate and repetitive inputs
7. Check for massively redundant/stressful inputs (i.e many successive clicks)
8. Verify that the nominal value of data is accepted, stored, retrieved, and displayed.
  • Related Links Widget for Blogspot

No comments: