VoidWorks Software Inc.
Detailed Design
Testing Plan
Document Navigator For The Design Index
Previous Section (Data Dictionary) Next Section (General Customer Q&A)

 

Testing Plan                                   

 

Objective                                   
     To locate any errors within the system as quickly and efficiently as possible and to correct them.

 

Testing Schedule                                   
      The scheduling is broken down per major area of development:
  • Book Administration Testing
  • Customer Administration Testing
  • Transactions Testing

    •  

    Testing Procedures                                   
         Unit Testing: incorporates the individual module testing for each part of the Customer Transaction section. Each module will be run through a set of tests that are used to determine correctness and consistency between the specifications and the actual prototype. Any errors encountered will be documented and returned to the programmers with a detailed description of the error and what the actual result should be. The unit testing will be performed according to the test schedule displayed above.
         Integration Testing: incorporates large sections of code utilizing more than one individual section. This would include any modules that require data from more than one data store. Integration testing will be performed according to the test schedule displayed above.

     

    Monitoring Procedures                                   
         Peter Woytiuk was appointed Head of Testing, and as such he will receive regularly scheduled reports on the progress of the current batch of tests. If testing is behind schedule, it is at his discretion to either extend the deadline, assign another tester to the current batch, or to drop the test altogether.

     

    Reporting and Correcting Procedures                                   
         If a bug or error is found, it's location is noted and in the case of any errors, the conditions which caused the error are taken down as well. The testers will then send this report to the Head of Testing, who will forward the report to the Programming Team. Once the bug has been corrected, another report is filled out listing what was done to correct the bug/error and how it was acheived. This will allow us to track any future bugs or errors which may arise during testing.

     

    Listing of Group Member Assignment                                   
         
    Head Of Testing
    Peter Woytiuk
     
    Test Coordinators
    Ian Byers
    Ryan Anderson
    Darrell Cobb
     
    Testing Teams
    Customer Functions
    Ian Byers
    Ron Dutton
     
    Book Functions
    Ryan Anderson
    Foster Lee
     
    Transaction Functions
    Darrell Cobb
    Dong-Hyun Kim
    Edward Chung
     
    Programming Team
    Bobby Wieler
    Ian Byers
    Darrell Cobb
     
    Report Manager
    Neil St. Laurent
     
    Customer Response
    Tom Mathewson
    Yi Wang
    Document Navigator For The Design Index
    Previous Section (Data Dictionary) Next Section (General Customer Q&A)

    Send mail to the Group Leader or the Webmaster
    Back to the Main Page
    Pages created and maintained with Mortar