Financials Testing
Testing plays a critical role in any software implementation process. Testing is needed to:
- Validate that CAPPS meets the agreed-upon requirements and functional designs;
- Verify that the system operates in an integrated fashion;
- Validate conversion of initial data from state legacy systems;
- Verify that user access to the system satisfies security requirements; and
- Verify that stress and performance tests meet state’s needs.
About the Testing Process
CAPPS testing is being performed through the HP Quality Center, a Web-based test management tool that offers an organized framework for testing applications before they are deployed. This tool helps to organize all phases of the application testing process by:
- Specifying requirements,
- Planning tests,
- Running tests, and
- Tracking defects.
CAPPS testing includes the seven major types listed below and runs from Jan. 24 through Aug. 5, 2011. Click on the Type of Testing to see the roles and responsibilities for participants in that cycle.
| Type of Testing | Definition | Example | Start Date |
|---|---|---|---|
| Functional Testing Cycle 1 | Tests specific functionality within a particular CAPPS module, including completed customizations. | Create and approve a requisition | 1/24/11 |
| Functional Testing Cycle 2 | Tests end-to-end business processes within a particular CAPPS module, including customizations. | Complete all steps in the requisition process and make payment | 3/28/11 |
| Accessibility Compliance Testing | Ensure CAPPS customizations meet state and federal accessibility guidelines. | Test accessibility tags to ensure JAWS can read the text | 4/4/11 |
| Integration Testing | End-to-end testing of business processes across CAPPS modules using converted data and security roles. Includes automated interfaces, workflows and reports. | Testing team tests end-to-end PO process: create requisition, approve requisition, budget check, create PO , approve PO , budget check, dispatch PO, receive goods, create payment, make payment and post to GL | 5/16/11 |
| Technical Testing | Range of testing to ensure that the technical infrastructure on which the application set resides operates as expected. | Verify the infrastructure connectivity (i.e. web server is connected to the application server) | 2/21/11 |
| Performance Testing | Testing to ensure the system is meeting ProjectONE-defined service-level objectives for online and batch operations. | Determine if system response time is acceptable | 2/22/11 |
| User Acceptance Testing (UAT) | Agency end users ensure overall production readiness of the integrated people, process and technology components through simulation of day-in-the-life critical process and functionality. Focus on demonstrating proper organizational handoffs and business interaction. | Agency end users test end-to-end PO process: create requisition, approve requisition, budget check, create PO, approve PO, budget check, dispatch PO, receive goods, create payment, make payment and post to GL | 7/4/11 |
