TRITECH SOFTWARE SYSTEMS 2 - Laserfiche WebLink

Home Browse Search

Module Identify the module to be tested Documentation Is the documentation for the topic correct? Compliance Does the product's operation comply with the specification as identified in the guide? Error Form Number Any associated testing error form regarding the topic Tester Initials Name of individual performing the testing Any area of non-compliance should be submitted on the testing error form. Printed samples of all erroneous output should be forwarded to the SAFD Project Manager immediately. These sample outputs will be used to identify and correct problems and update the as built documentation. Any items that do not operate as specified will be listed on a "Punch List". All items on the punch list will be corrected and retested prior to SAFD's passage of the product. Any errors and/or omissions in the as built documentation discovered during the testing phases will be reported and resolved. In some cases, the inconsistency will be corrected by modifying the documentation where there is no loss of required functionality. Such corrections must be made prior to system acceptance. Associated Interfaces Functional Acceptance Testing of the associated (internal/external) interfaces will be conducted following the development of said interfaces. All components will be tested and demonstrated to SAFD individually, and then as an overall system. The test scenario for the associated interfaces will ensure that a variety of requirements are met in the product, and in the case of the totality, the system. Any errors and/or omissions in the system manuals discovered during the testing phases would be reported and resolved in the same manner as problem/exception reporting described previously. The associated interfaces that will be tested include all of those identified in Exhibit B. The test plan assumes that interfaces have been developed and are live prior to the test period (failure to achieve live interfaces prior will delay the test start date as it is required for accurate testing). Testing Reporting Procedure All problems should be reported to the SAFD Project Manager using the approved Testing Error Form. The testers may be asked to follow up with reports, screen prints or other examples. To complete the form, the tester must furnish the following information: Priority Level Problems should be prioritized as follows: 1. Critical/High Priority - System is inoperable and/or data base integrity is endangered. 2. Critical/Low Priority - A major component is not fully operational; usage is restricted. 3. Non-Critical/High Priority - An application is not functioning correctly; however, the system is operable.