Suborbital-Systems/ReadySetGit
2
0
Fork 0
Code Pull Requests Packages Projects Releases Activity
24b358f205
ReadySetGit/Test-Suite.md

176 lines
13 KiB
Markdown
Raw Normal View History

initial import
2018-08-14 12:48:17 +00:00
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8"/>
<link type="image/png" href="assets/logo.png" rel="icon">
<title>ReadySet Markdown</title>
</head>
<script src="https://www.w3schools.com/lib/w3data.js"></script>
<body>
<topbar style="display:none;">
<item><a href="index.html">Overview</a></item>
<item><a href="plan.html">Project Plan</a></item>
<item><a href="index-all.html">Workflows</a></item>
<menu name="Themes"><item><a id="settheme"><b>Current</b></a></item></menu>
<toc></toc>
</topbar>
<xmp theme="readable" style="display:none;">
<!-- Markdown content here -->
GFM changes
2018-08-14 17:39:17 +00:00
# [QA Plan](qa-plan.html) > Test Suite
initial import
2018-08-14 12:48:17 +00:00
---
##### Project:
GFM changes
2018-08-14 15:28:58 +00:00
::[PROJECTNAME](Home)
initial import
2018-08-14 12:48:17 +00:00
##### Internal Release Number:
::X.Y.Z
##### Related Documents:
- [Test case format](test-case-format.html)
- ::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](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](use-cases.html) 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
<!-- Hint: turn off word wrapping to edit this big table -->
| BO \ Action | ::add | ::list/browse | ::edit | ::delete | ::search | ::other |
|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
| ::Student | <ul><li>::[student-add-1](test-cases.html#student-add-1)</li><li>::[student-add-2](test-cases.html#student-add-2)</li><li>::[student-add-3](test-cases.html#student-add-3)</li></ul> | ::[student-list-1](test-cases.html#student-list-1) | <ul><li>::[student-edit-1](test-cases.html#student-edit-1)</li><li>::[student-edit-2](test-cases.html#student-edit-2)</li></ul> | ::[student-delete-1](test-casesstudent-delete-1) | <ul><li>::[student-search-1](test-cases.html#student-search-1)</li><li>::[student-search-2](test-cases.html#student-search-2)</li></ul> | ::[See grid below](#enroll-grid) |
| ::Course | <ul><li>::[course-add-1](test-cases.html#course-add-1)</li><li>::[course-add-2](test-cases.html#course-add-2)</li></ul> | ::[course-list-1](test-cases.html#course-list-1) | <ul><li>::[course-edit-1](test-cases.html#course-edit-1)</li><li>::[course-move-1](test-cases.html#course-move-1)</li><li>::[course-add-prereq-1](test-cases.html#course-add-prereq-1)</li></ul> | ::[course-cancel-1](test-cases.html#course-cancel-1) | ::[course-search-1](test-cases.html#course-search-1) | ::N/A |
| ::Room | <ul><li>::[room-add-1](test-cases.html#room-add-1)</li><li>::[room-add-2](test-cases.html#room-add-2)</li></ul> | ::[room-list-1](test-cases.html#room-list-1) | ::TODO | ::TODO | ::TODO | ::N/A |
| ::Instructor | ::[inst-add-1](test-cases.html#inst-add-1) | ::N/A | ::[inst-edit-1](test-cases.html#inst-edit-1) | ::[inst-delete-1](test-cases.html#inst-delete-1) | ::N/A | <ul><li>::[inst-eval-1](test-cases.html#inst-eval-1)</li><li>::[inst-eval-2](test-cases.html#inst-eval-2)</li></ul> |
### ::Test Cases for Enrolling in Courses
| ::Course \ Student | ::New Freshman | ::Senior | ::Any Honors | ::Other |
|--------------------|----------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
| ::In Major | [::enroll-priority-2](test-cases.html#enroll-priority-2) | [::enroll-priority-1](test-cases.html#enroll-priority-1) | [::enroll-priority-1](test-cases.html#enroll-priority-1) | <ul><li>[::enroll-1](test-cases.html#enroll-1)</li><li>[::enroll-2](test-cases.html#enroll-2)</li><li>[::enroll-3](test-cases.html#enroll-3)</li></ul> |
| ::Non-Major | [::enroll-priority-2](test-cases.html#enroll-priority-2) | [::enroll-priority-1](test-cases.html#enroll-priority-1) | [::enroll-priority-1](test-cases.html#enroll-priority-1) | <ul><li>[::enroll-1](test-cases.html#enroll-1)</li><li>[::enroll-2](test-cases.html#enroll-2)</li><li>[::enroll-3](test-cases.html#enroll-3)</li></ul> |
| ::Honors Course | [::enroll-priority-1](test-cases.html#enroll-priority-1) | [::enroll-priority-1](test-cases.html#enroll-priority-1) | [::enroll-priority-1](test-cases.html#enroll-priority-1) | [::enroll-restricted-1](test-cases.html#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".*
- Essential
- ::[F-01](features#F-01):
::[student-add-1](test-cases.html#student-add-1)
::[student-add-2](test-cases.html#student-add-2)
::[student-add-3](test-cases.html#student-add-3)
- ::[F-02](features#F-02): [enroll-1](test-cases.html#enroll-1)
::[enroll-2](test-cases.html#enroll-2)
::[enroll-3](test-cases.html#enroll-3)
::[enroll-priority-1](test-cases.html#enroll-priority-1)
::[enroll-priority-2](test-cases.html#enroll-priority-2)
::[enroll-restricted-1](test-cases.html#enroll-restricted-1)
- Expected
- ::[F-22](features#F-22):
::[student-search-1](test-cases.html#student-search-1)
::[student-search-2](test-cases.html#student-search-2)
::[course-search-1](test-cases.html#course-search-1)
- ::[F-23](features#F-23):
::[room-add-1](test-cases.html#room-add-1)
::[room-add-2](test-cases.html#room-add-2)
::[room-edit-1](test-cases.html#room-edit-1) TODO
- Desired
- ::[F-31](features#F-31):
::[inst-eval-1](test-cases.html#inst-eval-1)
::[inst-eval-2](test-cases.html#inst-eval-2)
### 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
- ::[UC-01](use-cases#UC-01)
- ::[student-add-1](test-cases.html#student-add-1)
- ::[student-add-2](test-cases.html#student-add-2)
- ::[student-add-3](test-cases.html#student-add-3)
- ::[UC-02](use-cases#UC-02)
- ::[enroll-1](test-cases.html#enroll-1)
- ::[UC-03](use-cases#UC-03)
- ::[enroll-2](test-cases.html#enroll-2)
- ::[UC-04](use-cases#UC-04)
- ::[enroll-3](test-cases.html#enroll-3)
- ::[UC-05](use-cases#UC-05)
- ::[enroll-priority-1](test-cases.html#enroll-priority-1)
- ::[enroll-priority-2](test-cases.html#enroll-priority-2)
- ::[UC-06](use-cases#UC-06)
- ::[enroll-restricted-1](test-cases.html#enroll-restricted-1)
- Expected
- ::[UC-22](use-cases#UC-22):
::[student-search-1](test-cases.html#student-search-1)
::[student-search-2](test-cases.html#student-search-2)
- ::[UC-23](use-cases#UC-23):
::[course-search-1](test-cases.html#course-search-1)
- ::[UC-30](use-cases#UC-30):
::[room-add-1](test-cases.html#room-add-1)
::[room-add-2](test-cases.html#room-add-2)
- ::[UC-31](use-cases#UC-31):
::[room-edit-1](test-cases.html#room-edit-1) TODO
- ::[UC-32](use-cases#UC-32): TODO
- ::[UC-33](use-cases#UC-33): TODO
- Desired
- ::[UC-40](use-cases#UC-40):
::[inst-eval-1](test-cases.html#inst-eval-1)
::[inst-eval-2](test-cases.html#inst-eval-2)
<!-- End Markdown content -->
</xmp>
<div w3-include-html="_words-of-wisdom.html"></div>
<div w3-include-html="_footer.html"></div>
<script>
w3IncludeHTML();
</script>
<script src="http://strapdownjs.com/v/0.2/strapdown.js"></script>
<!-- Include it AFTER strapdown -->
<script src="assets/strapdown/strapdown-topbar.min.js"></script>
<!-- Include it AFTER EVERYTHING -->
<script src="assets/logo.js"></script>
<script src="assets/themeswitcher.js"></script>
</body>
</html>
Copy Permalink