Suborbital-Systems/ReadySetGit
2
0
Fork 0
Code Pull Requests Packages Projects Releases Activity
b48bb0e3c1
ReadySetGit/Test-Suite.md
William Sandner 6db4020baa Adjusted table formatting
2021-08-02 15:22:00 +02:00

10 KiB
Raw Blame History

Project

::PROJECT-NAME

Internal Release Number

::X.Y.Z

Related 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, functional 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 a way that will purposely leave visible blanks on this page if you are missing use cases. Choose one or more of the organizations show below.

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.

TIP: The test case suite can be organized into nested lists according to other coverage criteria, e.g., by actor. Or, it can be organized into tables that consider two aspects at a time, e.g., business objects vs. actor. If a certain section of the tree or table does not need test cases, explicitly mark it "N/A". Otherwise, if a section needs more test cases than you have written yet, mark it "TODO". If one cell or list item contains many tests, break that section out into its own table, as done for the enrollment feature below.

Test Cases by Business Object and Operation

BO \ Action ::add ::list/browse ::edit ::delete ::search ::other
::Student ::student-list-1 ::student-delete-1 ::See grid below
::Course ::course-list-1 ::course-cancel-1 ::course-search-1 ::N/A
::Room ::room-list-1 ::TODO ::TODO ::TODO ::N/A
::Instructor ::inst-add-1 ::N/A ::inst-edit-1 ::inst-delete-1 ::N/A

::Test Cases for Enrolling in Courses

::Course \ Student ::New Freshman ::Senior ::Any Honors ::Other
::In Major ::enroll-priority-2 ::enroll-priority-1 ::enroll-priority-1
::Non-Major ::enroll-priority-2 ::enroll-priority-1 ::enroll-priority-1
::Honors Course ::enroll-priority-1 ::enroll-priority-1 ::enroll-priority-1 ::enroll-restricted-1

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".

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".