The State of Tennessee's Enterprise Resource Planning Solution

Project Methodology
Test and Train Stage

The Test and Train stage is where the business processes, and associated software, that have been designed are brought to a production-ready state by system testing and by knowledge transfer to users. Below is a high-level process flow of activities relating to the Test and Train Stage:

1. Testing Conditions is the process where a set of functional conditions are developed that can be used to perform system/integration testing of the Edison system and associated business processes. These conditions range across module areas and enable cross-module and cross-application system test planning. The system test conditions are the “what” of system testing.
2. Test Scripts and Plan is where a set of functional test scripts are developed to perform system testing of the Edison system and associated software requirements. These scripts include module-specific test scripts, as well as cross-module and cross-application scripts. The scripts are designed to include all identified system test conditions. The system test scripts are the “how” of system testing.  Based on these scripts, the further goal is to develop a system test plan defining the “who” and “when” of system test conditions and system test scripts.
3. Perform Unit Testing of the baseline system functionality. Objects are tested for functionality, appearance, and processing metrics as compared to software documentation.  The test cycle only includes items judged to be core functionality by the project team. Non-core functionality and all modifications and customizations are designated by the project team as out of scope of unit testing.
4. Perform System/Integration Testing of Edison business processes as defined in the Business Process Design to meet all identified system test conditions. Testing incorporates delivered software processing and any modified or custom software objects.  Processes are tested for inputs and outputs, with actual results compared to the expected results defined in the System Test scripts.  A key component of integration testing is testing of cross-application interfaces, for example, interfaces from Payroll to Financials (i.e. General Ledger and Accounts Payable).
5. Perform User Acceptance Testing of certain Edison business processes to meet designated system test conditions.  Testing incorporates delivered software processing and any modified or custom software objects that are associated with the designated test conditions.  Processes are tested for inputs and outputs, with actual results compared to the expected results defined in the System Test scripts.
6. Perform Parallel Testing by running the legacy system payroll and Edison payroll for identical timeframes and produce quantifiable results for comparison. Although parallel testing is focused on payroll results, it includes participation across all Edison modules to assure that the Edison business processes and data are mimicking a production state.  Parallel testing is just another cycle of system testing with payroll results being the designated outcome.
   

Methodology

Analysis & Design

Construction

Test & Train