Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Lab 9 - Spring 2001 (Due 4/04/2001)
White Box Testing Lab
This lab is to be done in teams of 2 people - you select your partner.
You are given an application to test.
YOU DO NOT HAVE TO IMPLEMENT YOUR OWN SOLUTION!
Given the following problem and solution:
Highway Simulation Application
Test the application using WHITE BOX testing techniques.
White Box Testing Hints
White Box Testing is sometimes called "glass box testing," since you actually have access to the code to develop and run your test cases. But you should try to ignore the code and think of hard cases!
Mike talked in class about specific coverage measures:
Here are some suggestions:
- Statement coverage
- Branch/decision coverage
- Path coverage
Remember, a test case should be designed so that it can be recreated. It must include the following
- Design your tests cases to that you cover as many paths as possible, e.g., execute all loops at their boundaries
- Test all logical decisions at both true and false
- Try to ensure all statements are executed at least once
- Your test cases at a minimum should follow these suggestions.
- What is being tested - what criteria you used to select the test case
- What is the specific input - specific parameters, code, etc. used to create the result
- What is the expected output
We've introduced several bugs in the solution you are testing. But grading for this lab is not based solely on how many of them you are able to find. Instead, you will be graded on your ability to develop as complete a set of test cases as possible. But so that no one has to ask, the range of known bugs in the solution is 15-25.
Remember that solving one problem may create others. You should fix as many bugs as you can find, but you may need to rerun previous run tests to check for new defects. STRONG SUGGESTION: Use your defect log as a tool to track! You should keep a defect log recording any and all defects found and how you solved the problem. This can be done in a simple text file using the following table format:
| # || Date || Time || Description of Defect || Solution Attempted || Result |
Your corrected code should pass the test cases you've written and were able to correct.
- Test Cases, completeness, correctness, and format. 50%
- Corrected Code, passes your test cases. 25%
- Defect Log. 25%
What to turn in
- Text file containing all the test cases you wrote.
- l9.st file with corrected code.
- Text file containing your defect log.
- Turn in your Lab 9 submission to ONE TA, select from either partner's cs2340 group project TA.
Link to this Page