Ad hoc Testing Homework
This is an individual activity. Do not discuss this activity
with other students. If you have difficulties contact the instructor.
"Ad hoc" testing means testing without a plan. You
just improvise
some tests as you are interacting with the software. This is how
most students test their programs until they learn more formal
techniques. You just try whatever tests come into your mind as
you are executing the software.
Your assignment is to perform ad hoc testing on the Hangman software
developed by the Fish Bowl Games team. You are trying to
determine if there are any defects in the software. Don't spend
more than one hour on this activity.
1. Go to the Fish
Bowl Games home page and locate the links to the SRS, User Manual,
and Download Page.
2. Follow the installation instructions in the User Manual to
install the Release 2 Hangman product on your workstation. You
should be able to
- Start the WordServer.
- Start the game with the text user interface.
- Start the game with the graphical user interface.
3. Read the SRS and the User Manual to
understand how the software should behave. (You can skip the
section on using Instant Messaging to interact with WordServer.)
4. Execute the Hangman software and attempt to determine if
it behaves as specified. Keep a log (neatly handwritten or typed)
of all the tests you try.
Record the exact data values you enter. Note the results of each
test, indicating "OK" if the actual output was as expected, or
"FAIL" if the actual output was different than predicted. If the test
fails, describe the discrepancy between the expected output and actual
output.
4. Type up a brief conclusions section which summarizes the test
results. Comment on the nature of problems you encountered. Distinguish
software failures from other kinds of failed tests:
A) Software fails to conform to specification:
Input data which produce outputs other than what is predicted.
Unexpected abnormal termination - "crashing."
Any behavior not consistent with the specification.
B) Other test failures.
Specification or User Manual are incomplete or ambiquous.
Any system event which the specification hasn't anticipated.
Inputs for which the specification doesn't define a response.
Outputs not predicted or defined in the specification.
Document History
Date
|
Author
|
Description
|
4/7/06
|
JD
|
Initial Release
|