Homework 3: Testing

Due date: Thursday, March 31, at the beginning of class

1. System Test Cases (40 points)
Divide up the use cases of your project among team members, so that each member gets assigned an equal number. Each member shall develop a total of 16 system test cases for the use cases assigned to him or her. Each use case shall employ a number of different test data. Include boundary values as appropriate. Adhere to the test case format specified here (examples are here).

2. Bugs (20 points)
Find 3 bugs of severity level A or B in your team's product. For each bug, write down the exact steps and input values needed to reproduce the bug, and state the expected result and the actual result.

3. Update Unit Test Cases (30 points)
Update your unit test cases from Homework 1: first, make sure they still work with the current version of the program, and 2, add test cases for parts of the program that do not have unit test cases yet. As before, coordinate with your team members to avoid duplication. There must be at least one unit test case for each non-trivial operation in your program. Hint: if you have not yet used a unit testing tool in Homework 1, this might be a good point to start doing so. Turn in a printout of your unit test cases in code.

4. Test Plan (10 points)
Write a draft test plan for your project. Discuss what kinds of testing (system testing, usability testing, stress testing, performance testing and so on) needs to be performed, and what kinds of resources (tools, people, time...) are needed to do so.


CS 498 Spring 2005