Laserfiche WebLink
Otston:er Process Tests - Customer Process testing represents a final verification that all related system <br />components are working together with ,nQuestaT'" confi;ured specifically to emalate customer - specific <br />1 u�,ntess practices. Tc .t scripts ;an be prepared by the customer fi-om example test cases to validate the entire <br />husmess processes as derived fron, the process analysis or modific,ztion documentation. This phase is ty icaH <br />pert'viu cd with customer data converted �rnd in place and product Configuration complete. C ustomer Process <br />te:,tinw* \.I ill ensure that euQUesta; "' is functioning as expected and desired with the final Coll Ei1-Iu.:ltion, codin" <br />and testing phases above complete. <br />B. Integration Testing (i.e., processes /functionality that relies on integration between modules, including 3rd party <br />software that is part of the proposal, is working properly). <br />LaiNson Response: L.awson's approach to to tin(' is continual and iterative throughout the implementation. <br />Our methodology includes unit, prototype, system inter *ration, reL- ession and acceptance testing. La.h testing <br />phase is Conducted in collaboration with the City and the City team is expected to sign off on the result,, before <br />proceeding to the next phase. Testing is based upon end -to -end business scenarios. A business scenario <br />operates across multiple system modules and common procedures. Each business scenario is organized and <br />documented by process step and application step. Each integration test represents a specific business scenario <br />and is formulated by considering the objectives, but constructed fi -om details contained in the conference room <br />pilot test documentation. An integration test consists of several test cases strung together end -to -end. Defects <br />identified are to be corrected by Lawson and the City implementation team. �ollowing error correction, <br />regression testing will be performed which includes the retesting of business transactions until the scenario is <br />completed successfully. <br />The methods used during the various phases of testing are: <br />Testing Phase <br />Testing Method <br />Unit <br />Manual execution of test scripts using a subset of converted or manually_ <br />entered data. <br />Prototype (Conference Room <br />Pilot) <br />Requirements -based test scripts by functional area. <br />Manual execution of test scripts. <br />Inspection of user test results and reports using a subset of converted or <br />manually entered data. <br />System ,Integration and Parallel <br />Requirements -based test scripts by functional area. <br />Manual execution of test scripts. <br />Inspection of user test results and reports using interfaced and <br />converted data. <br />Regression <br />Execution of manual test cases, as needed. <br />Inspection of user test results and reports using interfaced and <br />converted data. <br />Acceptance <br />Validation of the systern rather than verification. <br />Execution of selected scenarios similar to the system and integration <br />tests, but geared toward the users' view of the application. <br />S &S Response: In terms of integration testing, we will complete an initial functional and technical test to <br />verify that all related system components are working together. Test scripts can be prepared from the test cases <br />to validate the entire business processes as derived from the process analysis or modification documentation. <br />Integration testing will also test batch job streams. This phase is typically performed with minimal data and is <br />executed to properly time specific business events and their interdependencies. <br />C. Stress /Load Testing (i.e., the entire system works in terms of response time, load time, and stress). <br />Lawson Response: Lawson's recent experience has been that our clients do not require stress testing due to <br />improvements in hardware, networks, databases, and software solutions in recent years. Stress testing <br />primarily was needed in the past due to highly customized solutions. Lawson internally stress tests its solutions <br />prior to general availability and provides server sizing metrics based upon peak performance requirements. <br />Lawson has not included hours in its estimate to assist the City with stress testing, however, should the City <br />Lawson Software - Confidential 48 <br />