Test Case Analysis

This defines what to keep in mind as you plan how to test software.

TMap Next, Business Driven Test Management (UTN Publishers, 2008-11-28) by Leo van der Aalst, Rob Baarda, Ewald Roodenrijs, Johan Vink, Ben Visser

Software Testing: A guide to the TMap Approach (Addison-Wesley, 2001) by Martin Pol

Topics this page:

Related Topics:

Site Map  
About this site  

Database State

This Statechart created using Visio 2000 with the UML Software Add-on identifies the various states of a database used for testing.

1. When an application is first installed (New), the user database is not populated (Empty).
   
2. The new database may be Configured with information such as country, users, groups, and other data referenced by normal user processing activity.
   
3. After users perform transactions using the application's GUI, the database has been Changed with GUI.
   
4. The database also may be Updated with a Batch run that is in parallel or complimentary to changes resulting from user GUI actions.
   
5. Testing can also begin from a database that has been Populated by a previous test step.
   
6. The application may include processing that results in the database being converted from another data format or even another database schema. How accurate and complete was that?
   
7. Optionally, the database could be cloned (copied) in a batch run or replicated in real time. This involves changes to data values (but not the database structure). This process could introduce errors.

Verifying Check Boxes

If users have only a binary choice to select for a control, such as Yes/No or checked/unchecked, there are actually four or more possible test runs. Generate reports, extract files, or verify other processing after each of these AnalLists are established:

1. Empty (no answer either way), the default condition after blank database initialization.
2. Yes after interactive manual update using the GUI.
3. Yes still, but with its parent function or container disabled (not selected), to verify logical integrity. If there are several logical dependencies, then this test needs to be extended.
4. No after interactively resetting value in the database.

If users have a set of fields, each with different values, then plan tests using a matrix of possible value sets: For example, with a checkbox and a value:

#	Checkbox value	Field value
1.	UnChecked	empty
2.	UnChecked	filled with valid value
3.	UnChecked	filled with invalid value
4.	Checked	empty
5.	Checked	filled with valid value
6.	Checked	filled with invalid value

There would be more test cases if there are different possible valid values and/or different types of invalid values.

...

Verifying Lists

If users have a list of check boxes to select:
1. All Empty (no answer either way), the default condition after blank database initialization.
2. All Yes after interactive manual update using the GUI. This is a good base to compare all labels for values in GUI vs. reports.
3. All Yes still, but with its parent function or container disabled (not selected), to verify logical integrity. If there are several logical dependencies, then this test needs to be extended.
4. All No after interactively resetting value in the database.
5. A combination of Yes and No, such as in this alternative pattern makes it easy to spot extra or missing items.
   • Y
   • N
   • Y
   • N
   • Y
   • N
6. Reverse the values and run it again to ensure that all values are processed properly.

...

Verifying Numbers with Boundary Value Analysis

In a numeric field such as age, not all possible values (from 0 to 120) need to be tested. Only values in the boundary need to be tested:

A#	B#	Data Value	Test Description	Expected Response
8.	1.	5	Minimum allowable	Pass: Should accept
7.	2.	6	One greater than minimum	Pass: Should accept
6.	3.	120	Maximum allowable	Pass: Should accept
5.	4.	119	One less than maximum.	Pass: Should accept
4.	5.	121	One more than maximum.	Fail: Server check issues error message.
3.	6.	0	"Newborn"	Fail: Client-side Error: Below minimum age.
2.	7.	-1	Negative Value	Fail: Keypress prevents entry. Server check issues error message "Not allowed"
1.	8.	blank	Blank	Fail: Server check issues error message "Not allowed"

The two test item numbers are for two different passes of testing:
The "A" sequence begins with invalid values and ends with valid values (the normal user sequence).
The "B" sequence begins with valid values and ends with invalid values.

Then the LORD said, "My Spirit will not put up with humans for such a long time, for they are only mortal flesh. In the future, they will live no more than 120 years." —Genesis 6:3 (NLT)