Test Cases and Results

Type of Test Case: Validation

Vigo County School Scheduling Application

Team H

Test Table

ID /
Description 		Input Tester Name /
Test Case Type /
Date Executed 		Actual Result
  • 01
  • Test whether or not school information can be properly entered and edited by doing so in the interface.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 02
  • Test whether or not grades can be added and edited correctly to the application through the interface.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 03
  • Test whether or not teachers and their constraints can be properly added and edited in the application via the user interface.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 04
  • Test whether or not students can be added and edited correctly through the interface.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 05
  • Test whether or not general education times can be added to a teacher's Stage 1 schedule appropriately throough the interface.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 06
  • Test whether or not the schedule generation algorithm correctly creates master and teacher schedules and stores them in the application's data.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 07
  • Test whether or not a student's schedule can be correctly found and displayed in the interface.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 08
  • Test whether or not new or additional teachers can be imported into the application from a designated csv file containing such data.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 09
  • Test whether or not new or additional students can be imported into the application from a designated csv file containing such data.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 10
  • Test whether or not the weekly schedule for a specials class can be correctly exported to a spreadsheet file.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 
  • 11
  • Test whether or not the weekly schedule for an individual teacher can be correctly exported to a spreadsheet file.
 OK: 
  • <input/output description> 
ERROR:
  • <input/output description> 
  • <Tester name> 
  • <MM/DD/YYYY> 
 PASS: 
  • <pass item and result> 
FAIL:
  • <fail item and result> 

Tallies

Total Number of Test Cases Total Number of  Test Cases Executed Total Number of Test Cases that Completely Pass Total Number of Test Cases with Failures
12 0 0 0