The following tests should be implemented before the code for these user-stories is started. They will ensure that that the code for these sub-sections is correct. We haven't discovered a way to automate these tests at this time. This is simply documentation on the test cases that should be run.
Unit Tests For Following User Story
| Date: | 11/12/00 | Type of User Story (New/Fix): | Fix |
| Story Number: | 18 | Time Estimate: | 2 weeks |
| Story description: | |||
| Professors can add a grade listing to the gradebook. | |||
Definitions:
Grade Listing - a specific grade type in the gradebook. For example, HW1, MIDTERM1, etc.
Test Case Requirements
The Following User Types (or Users w/ following access permissions/titles) are needed in the system to run these test cases.
These users must have the access to modify/change grades in the same class.
Professor #1
TA #1
Unit Test Cases:
Test #1:
Professor #1 logs into system
Professor #1 enters grade listing entry form
Professor #1 enters new grade listing
Professor #1 confirms new grade listing has been added
Professor #1 has the option of adding another grade listing or quiting
Test #2:
Professor #1 logs into system
Professor #1 enters grade listing entry form
Professor #1 enters new grade listing that has the same name as another grade listing
Professor #1 recieves message notifing him operation has failed due to duplicate listing
Professor #1 has the option of adding another grade listing or quiting
Test #3:
Professor #1 logs into system
Professor #1 enters grade listing entry form
Professor #1 enters new grade listing that has an invalid name
Professor #1 recieves message notifing him operation has failed due to invalid name
Professor #1 has the option of adding another grade listing or quiting
Test #4:
TA #1 logs into system
TA #1 attempts to open grade listing entry form and is denied access
Unit Tests For Following User Story
| Date: | 11/12/00 | Type of User Story (New/Fix): | Fix |
| Story Number: | 19 | Time Estimate: | 1 week |
| Story description: | |||
| Professors and administrators can add and delete students from the course's gradebook. | |||
Gradebook - Database of student grades in various courses
Unit Tests:
The Following User Types (or Users w/ following access permissions/titles) are needed in the system to run these test cases.
These users must have the access to modify/change grades in the same class.
Professor #1
Administrator #1
TA #1
Part One - Unit Test Cases For Addition
Test #1:
Professor #1 logs in to system.
Professor #1 enters add/del student form.
Professor #1 chooses add and enters student net id.
Professor #1 recieves message signifying successful addition to gradebook.
Test #2:
Professor #1 logs in to system.
Professor #1 enters add/del student form.
Professor #1 chooses add and enters duplicate student net id.
Professor #1 recieves message signifying unsuccessful operation due to duplication.
Test #3:
Professor #1 logs in to system.
Professor #1 enters add/del student form.
Professor #1 chooses add and enters invalid student net id.
Professor #1 recieves message signifying unsuccessful operation due to bad net id.
Test #4:
Administrator #1 logs in to system.
Administrator #1 enters add/del student form.
Administrator #1 chooses add and enters student net id.
Administrator #1 recieves message signifying successful addition to gradebook.
Test #5:
Administrator #1 logs in to system.
Administrator #1 enters add/del student form.
Administrator #1 chooses add and enters duplicate student net id.
Administrator #1 recieves message signifying unsuccessful operation due to duplication.
Test #6:
Administrator #1 logs in to system.
Administrator #1 enters add/del student form.
Administrator #1 chooses add and enters invalid student net id.
Administrator #1 recieves message signifying unsuccessful operation due to bad net id.
Part Two - Unit Test Cases For Deletion
Test #1:
Professor #1 logs in to system.
Professor #1 enters add/del student form.
Professor #1 selects student id and chooses delete.
Professor #1 recieves message signifying successful deletion from gradebook.
Test #2:
Professor #1 logs in to system.
Professor #1 enters add/del student form.
Professor #1 does not select an id and chooses delete.
Professor #1 recieves message signifying no id selected.
Test #3:
Administrator #1 logs in to system.
Administrator #1 enters add/del student form.
Administrator #1 selects student id and chooses delete.
Administrator #1 recieves message signifying successful deletion from gradebook.
Test #4:
Administrator #1 logs in to system.
Administrator #1 enters add/del student form.
Administrator #1 does not select an id and chooses delete.
Administrator #1 recieves message signifying no id selected.
Part Three - Unit Test Cases For Unauthorized Users
Test #1:
TA #1 logs in to system.
TA #1 attempts to open add/del student form.
TA #1 denied access to add/del student form.