TRITECH SOFTWARE SYSTEMS 2 - Laserfiche WebLink

Home Browse Search

Functional Test Criteria The purpose of this document is to provide the structure, parameters and forms to be used during Functional Testing of the TriTech products (CAD, MOBILE and Associated Interfaces). During the testing process, a command -by -command test of the system to ensure the system functions as indicated by TriTech in their RFP response, the as -built documentation and the configuration list developed in Task 1-C. Methodology The following defines the general test procedure: • Problem/Exception Reporting - Throughout the testing cycle, unexpected results, problems, and/or exceptions will be formally logged and reported immediately to SAFD's Project Manager, using an approved Testing Error Form. Printed forms will be supplied to each tester prior to commencement of testing. Problem/Exception Resolution - Newly reported problems will be examined by both SAFD and TriTech personnel. TriTech will examine the problem, then develop and deliver a fix or patch. Should an error occur that impedes the operation of the product, TriTech will work continuously until the error is corrected. Should an error occur that impedes the proper operation of a module, or a large component of a module that would prevent the use of the module, or should any other error be reproducible and definable, TriTech will correct the error prior to functional testing passage. Failure to correct such errors will prevent task completion, and system acceptance (that is to say the acceptance of both the product as well as the total system). TriTech will notify the SAFD when recorded problems have been resolved. SAFD will then retest the item(s) by prioritizing newly completed fixes over the scheduled test plan. • Additional Testing - As problems are discovered, additional testing may be required to confirm that they have been resolved. SAFD will continue the test process even though additional problems may be found (unless SAFD and TriTech jointly agree that a problem or set of problems makes continued testing impractical). • Test Completion - Once the test cycle is complete, defects identified during the test as Priority 3 — 6 will be included on the systems' "Punch List". Resolution of this Punch List is part of the software process and will not preclude user training and implementation. Additional problems that may be found outside of this list will be resolved through normal warranty procedures. Functional Testing Procedure Functional Testing is a command -by -command test of the product to ensure that the product functions per the RFP response, the as -built documentation and the configuration list developed in Task 1-C. Using these documents, SAFD will craft a controlling document which identifies each of the product's transactions, commands, screens, displays, functions and features to be tested. The testing of each module should be executed using a standard format by all testers, using the test guide (a simple format to be developed by SAFD 30 days prior to testing) to validate each module's functionality, noting the following: Date Date the individual performs the testing Product Name of product being tested