Release Information
Project: |
PROJECT-NAME |
Internal Release Number: |
X.Y.Z |
Related Documents: |
LINKS-TO-RELEVANT-STANDARDS
LINKS-TO-OTHER-DOCUMENTS
|
Process impact: This is a test suite for
manual system testing. It is just one activity in the overall
QA plan. A test case suite is simply a table
of contents for the individual test cases. Organizing the suite of
test cases by priority, feature area, actor, business object, or
release can help identify parts of the system that need additional
test cases.
TODO: Before writing individual test cases, list the test cases that
you think you will need. Organize them in trees or tables that
leaves visible blanks on this page if you are missing test cases.
If a blank section of the tree or table does not need test cases,
explicitly mark it "N/A", otherwise, mark it "TODO". If one cell or
list item contains many tests, break that section out into its own
table, as done for the checkout feature below. Choose one or more
of the organizations shown below. See the
test case format reference page for
more tips on specifying tests and test suites.
TIP: Refer back to your
use cases
document. Use them for ideas and make sure that you cover all of
them. Remember that test cases are more precise than use cases,
test cases should reference specific details of your implementation,
and there may be several test cases for a given use case.
Test Cases by Business Object and Operation
BO \ Operation |
Add |
List/Browse |
Calculate |
Edit |
Delete |
Search |
Other |
User |
register-1
|
N/A
|
N/A
|
edit-profile-1
edit-profile-2
|
TODO
|
N/A
|
password-replacement-1
account-lockout-1
|
Product |
TODO
|
TODO
|
See inventory grid below
|
TODO
|
TODO
|
TODO
|
TODO
|
Order |
TODO
|
TODO
|
TODO: Shipping and sales tax
|
TODO
|
N/A
|
N/A
|
TODO: checkout
|
Store Dept |
TODO
|
TODO
|
TODO: traffic and sales stats
|
TODO: select featured products
|
TODO
|
TODO
|
TODO
|
Prod. Review |
TODO
|
TODO
|
TODO: Average rating
|
TODO
|
TODO
|
TODO
|
TODO
|
Test Cases for Product Inventory Status
Test Cases by Feature Priority
TODO: Use this outline to make sure that high priority features are
adequately tested. List features by priority, and then list the test
cases for each feature. If a feature needs more test cases, note
that with "TODO".
- Essential
- Expected
- Desired
- Optional
Test Cases by Use Case Priority
TODO: Use this outline to make sure that high priority use cases are
adequately tested. List use cases by priority, and then list the
test cases for each use case. If a use case needs more test cases,
note that with "TODO".
- Essential
- Expected
- Desired
- Optional