INFOR (US) INC. (FORMERLY LAWSON SOFTWARE) 2 - 2008

Home Browse Search

S &S Response: During the Design Phase of the implementation, we will develop a testing plan. which shall detail the testing approach, methods, data participants, roles and responsibilities, deliverables and milestones. Our , �%stcrn testitrg encompasses functional and process testing th -il includes Cie :onf g red solution, nioditications, interfaces, reports and the CIi,v's cony . -rted data. This testin-, will verify cress- functional full life- c,.cle Testing. The City`, te; m will be involved in the process testing �,,nd validzttion process throughout the implementation. Our software testing approach is comprised of several phases, each one supported by specific tools and methodologies required to ensure an accurate and complete systems test. IJach phase is carefully planned and d,)CUtnented through a formal test plan. This plan is developed by our core teann and will identify the testing approach and methods, participants, and responsibilities required for sueeessfld product testing. We gill oversee the pianning for all systems test phases, as well as the execution of the test plan with customer ownership and participation in the final customer process testing phase. For the implementation protect, we will provide standard test cases to your project team that can provide a thorouuh test of the system. These test cases are geared toward core enQuestaTM ttmctionality. Test scripts can be prepared from the identified cases and include the required data, the processes to be run and the expected results. A phased test work plan is developed which includes detailed tasks, responsibilities and timeiraunes 1 °or each major data test phase step listed below. These test phases typically include: Unit Test - Each code change, enhancement or modification is defined as a single object or a group of contained objects or process. Fach object is to be unit tested prior to release for further testing outside of the development channel. Although primarily completed in the Business Process Mapping and Development phases, a checklist of all individual processes. reports and programs either delivered by enQuestal 11-1 or custom developed, need to be completed. Integration Test - This represents an initial functional and technical test to verify that all related system components are working together. Test scripts can be prepared from the test cases to validate the entire business processes as derived from the process analysis or modification documentation. Integration testing will also test batch job streams. This phase is typically performed vvith minimal data and is executed to properly time specific business events and their interdependencies. Load Test - This phase attempts to determine any all performance problems in the operation of the system by performing high volume tests. Typically, a subset of test cases from the test plan are used, choosing online, batch and query processes that may be considered suspect under high volume conditions. Benchmarks are taken at minimum volumes so that a comparison can be made. High volumes of test data are created on the system and peak user simulation transactions are used to stress the system. Conversion Test - 'I"his test leverages the test cases of the integration test phases, but is executed with actual converted data. This often becomes the basis for the production system. In order to be ready for the actual data conversion, enQuestaTM11 is tested with your actual data upon each conversion phase. Not only will we identify any gaps in data received from your old system, but we will fix or code changes that may be necessary to support the system. Regression Test - Regression testing is performed on all test scripts that may be affected by the implemented fix to verify that the fix works and has no effect on other related processes. Issues that arise during the testing process are immediately logged into our Test Track Pro issue tracking system. Once an issue is submitted, all issue number and priority code are assigned and the issue is routed to the appropriate Subject Matter Expert for resolution. When a resolution is provided, the issue is tested by our team. Passing test results prompt us to deploy the issue fix to your test environment. Nklen your team has tested the fix and notifies us of satistactory results, we will then deploy the fix into the live production environment. Lawson Software — Confidential 47