Test Specifications

							      Sample Test Specification Form (a sample of 1 completed page out of 8 pages for
      this team.)

                                                   EMS IMPACT System Test Specifications
In order to fully test our system, we plan to use a combination of black and white box testing methods.

Black Box
As developers, we will follow our test specifications to ensure that each set of inputs generates the correct outputs. After entering test data, we will also
generate each report and make sure they show the correct output. However, we know we have a limited perspective on the system. Therefore, we will
provide copies of the test system to our user sponsor and ask him, and anyone else interested in helping, to “break” it.

White box
After the bulk of the code is completely written, each team member will take a section of code written by someone else to look for both coding errors and
opportunities to make the code more efficient.

Test Specifications

       Test Condition       Description of Condition                        Test Steps                            Expected Results              Results
      Select SR-1          Enter a future date                 Enter 12/12/99 at the date prompt         System should reject the entry &
                                                                                                         clear out the field
      Select SR-2          Enter an invalid date               Enter 13/1/96, 2/45/97, and 2/31/97       System should reject the entry &
                                                                                                         clear out the filed
      Select SR-3          Enter an Invalid Employee           Instead of choosing from the drop         System should reject and require
                                                               down of employees, enter “Joe             that the selection be on the list
                                                               Smith”.
      SRButtons-1          Test Undo Button                    Start a new record. Enter data in one     Undo button should become
                                                               field. Repeat this process with every     enabled
                                                               field on the screen for every tab
      SRButtons-2          Test Previous Button                Scroll through multiple records for       Until you hit the first one, the
                                                               an employee for all tabs                  Previous button should work & be
                                                                                                         enabled
      SRButtons-3          Test Next Button                    Scroll through multiple records for       Until you hit the last one, the Last
                                                               an employee for all tabs                  button should work & be enabled
      SRButtons-4          Test Save Button (leave             For each required field, try saving       System should give an error and
                           required fields blank)              leaving it empty. Repeat for each tab     not allow save.
      SRButtons-5          Test Delete Button                  Delete an entry. Do this for all tabs     Scroll back through records. The
                                                                                                         entry should not be there.
      SRCrew-1             Enter invalid Division, not on      Enter “Test” as a Division                System should give an error and
                           list                                                                          not allow entry
      SRCrew-5             User categorizes comment as         Select Concern from the Category          The Personnel Action button
                           “Concern”                           list                                      should appear