
Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Material Type: Assignment; Professor: Coppit; Class: Software Engineering; Subject: Computer Science; University: William and Mary; Term: Spring 2004;
Typology: Assignments
1 / 1
This page cannot be seen from the preview
Don't miss anything!
Working in groups of two, create a set of testing artifacts for the 3D version of the Billiards project: a use cases document, a unit testing plan, and a system/integration testing plan.
Enhance the use case document to provide a complete set of use cases for all user-level interactions with the software. Be sure to include multiple scenarios if appropriate, as well as error scenarios.
Create a test plan for the testing of the modules of the system. Given that we have been fairly good about testing the modules so far, it is sufficient to provide a general set of rules for testing modules, plus some specific tests which should be run.
For example, your test plan may state that every non-user interface module must use fully automated testing, and that every method must have a test case. Then, in a subsection for each module, you may include additional module-specific tests. Remember that your test plan is meant to ensure that the modules are “solid”.
We’ll combine system and integration testing in the last document. Document a sufficiently complete set of test cases for the interactions between the modules of the system. In addition, describe a set of tests which can be done on the entire system.
You may want to research GUI testing tools. If you find a suitable one, you can define your test cases using the tool, but be sure to explain them so that I can grade you. If you intend for the system-level tests to be performed manually, you must describe each test case in enough detail so that a trained pigeon could execute the test and verify the results.
100 points total. Both students receive the same grade.
I expect there will be some concern over the level of detail that I will require. Your tests should use the requirements document as a starting point. Obviously some requirements can not be tested and must be verified manually. On the other hand, some testable requirements are missing. Your test plan should be detailed enough so that if the software passes the test plan, you can be sure that the customer will be happy.
If you have any questions, feel free to ask them in the discussion forum.