Test Cases and Results

Type of Test Case: <Fill in with "Validation", "Integration" or "Unit">

<Project Name>

<Test Case Authors>

<Note: everything surrounded by <> is either a placeholder to be filled in or a comment to be deleted when submitting each Test Case.>

Test Table

<The test table has the following entries:

ID / Description - Unique test case id (test case file number - which should be the same for each case in a particular file, followed by a dot, followed by an id where numbering starts at 1) and brief summary of what this test addresses
Input / Expected Output - bulleted list of a brief description of the type of input and expected output used in performing the test
Tester Name / Date Executed - Name of individual performing the test, when the test is executed (only execute a test case if the software portion it is supposed to check is implemented)
Actual Result - Bulleted list of PASS and FAIL items and what the actual result is

Entries should be organized well so that similar tests are close to each other.

If the test is executed several times, then each execution should be recorded underneath the corresponding test entry by adding an additional row and recording the Tester, Date Executed, and Actual Result. If the Tester doing the additional execution deletes or adds input items to the test case, then record that in his/her Input / Expected Output column.

In order to keep the table as small as possible, each entry should correspond to a test case that thoroughly checks one element, subfunction, or sequence of actions for the item (the item may be a unit, integrated set of units, or the complete software). For example, you might check a text field in a user interface with many combinations of input, such as no text, text over the max number of characters, text with special characters, and normal text. Such entries might look like:

ID /
Description Input /
Expected Output Tester Name/
Date Executed Actual Result

5.1

Checks the username field in the login screen to be sure that erroneous logins are not allowed

Correct password used where applicable with:
OK:

correct username

ERROR:

no text

text > max characters

text with special characters

Jane Smith

9/18/2002

PASS:

correct username (logged user in)

no text (did not log user in and gave appropriate error message)

FAIL:

text > max characters (logged user in, input: maximumcharacters)

text with special characters (generated run-time error, input: y&8*9#)

ADDED:
OK:

none

ERROR:

text with control characters

John Woods

9/22/2002

PASS:

all

FAIL:

none

5.2

Checks the password field in the login screen to be sure that erroneous logins are not allowed

Correct username is entered with:
OK:

correct password

ERROR:

no text

text > max characters

text with special characters

Jane Smith

9/18/2002

PASS:

correct password (logged user in)

no text (did not log user in and gave appropriate error message)

FAIL:

text > max characters (logged user in, input: maximumcharacters)

text with special characters (generated run-time error, input: y&8*9#)

The actual table to use is below. Use as many rows as you need.>

ID /
Description Input Tester Name /
Test Case Type /
Date Executed Actual Result

<test case file number>.<ID>

<brief description of the test>

OK:

<input/output description>

ERROR:

<input/output description>

<Tester name>

<MM/DD/YYYY>

PASS:

<pass item and result>

FAIL:

<fail item and result>

<test case file number>.<ID>

<brief description of the test>

OK:

<input/output description>

ERROR:

<input/output description>

<Tester name>

<MM/DD/YYYY>

PASS:

<pass item and result>

FAIL:

<fail item and result>

<test case file number>.<ID>

<brief description of the test>

OK:

<input/output description>

ERROR:

<input/output description>

<Tester name>

<MM/DD/YYYY>

PASS:

<pass item and result>

FAIL:

<fail item and result>

Tallies

<The table entries are:

Total Number of Test Cases - total number of test case entries in the test table above (excluding additional execution entries)
Total Number of Test Cases Executed - total number of test cases executed in the test table above
Total Number of Test Case that Completely Pass - total number of test cases in the test table above on which the software worked correctly
Total Number of Test Cases with Failures - total number of test cases in the test table above on which the software did not work correctly

For the example table above, this table would look like:

Total Number of Test Cases	Total Number of Test Cases Executed	Total Number of Test Cases that Completely Pass	Total Number of Test Cases with Failures
2	2	1	1

Place a 0 in each column if no tests have been performed yet. The actual table to use is below.>

Total Number of Test Cases Total Number of Test Cases Executed Total Number of Test Cases that Completely Pass Total Number of Test Cases with Failures

<# of test cases> <# executed> <# passed> <# failures>

ID / Description	Input / Expected Output	Tester Name/ Date Executed	Actual Result
5.1 Checks the username field in the login screen to be sure that erroneous logins are not allowed	Correct password used where applicable with: OK: correct username ERROR: no text text > max characters text with special characters	Jane Smith 9/18/2002	PASS: correct username (logged user in) no text (did not log user in and gave appropriate error message) FAIL: text > max characters (logged user in, input: maximumcharacters) text with special characters (generated run-time error, input: y&8*9#)
	ADDED: OK: none ERROR: text with control characters	John Woods 9/22/2002	PASS: all FAIL: none
5.2 Checks the password field in the login screen to be sure that erroneous logins are not allowed	Correct username is entered with: OK: correct password ERROR: no text text > max characters text with special characters	Jane Smith 9/18/2002	PASS: correct password (logged user in) no text (did not log user in and gave appropriate error message) FAIL: text > max characters (logged user in, input: maximumcharacters) text with special characters (generated run-time error, input: y&8*9#)

ID / Description	Input	Tester Name / Test Case Type / Date Executed	Actual Result
<test case file number>.<ID> <brief description of the test>	OK: <input/output description> ERROR: <input/output description>	<Tester name> <MM/DD/YYYY>	PASS: <pass item and result> FAIL: <fail item and result>
<test case file number>.<ID> <brief description of the test>	OK: <input/output description> ERROR: <input/output description>	<Tester name> <MM/DD/YYYY>	PASS: <pass item and result> FAIL: <fail item and result>
<test case file number>.<ID> <brief description of the test>	OK: <input/output description> ERROR: <input/output description>	<Tester name> <MM/DD/YYYY>	PASS: <pass item and result> FAIL: <fail item and result>