| Question | State 1 | State 2 | State 3 | State 4 | State 5 |
| State or County administered? | State managed / County Administered | State managed / County Administered | State Managed and Administered | State Managed / County Administered | State Managed and Administered |
| Current Phase? | Maintenance | Maintenance | Maintenance | Statewide Implementation | Maintenance |
| Vendor and State responsibility for testing - Initial Development? |
Vendor:
Unit, System, Regression Testing, Conversion. (Supported UAT) State: UAT/QA and Conversion. |
No vendor | Vendor:
Unit and system testing. State: UAT Scripts created together. Schedule slip caused them to combine system and UAT testing. |
State and vendor work side-by-side throughout process. | Vendor:
Unit, integration, and system test. State: Supports system tests. UAT team is managed by state, but vendor business analysts are included on team on time and materials contract. |
| Vendor and State responsibility for testing - Maintenance? | Vendor: Unit, System, Regression Testing. (Supports UAT/QA during staffing shortages - does not recommend this practice) | No vendor | Vendor is time and materials, so State controls. | NA - not in maintenance yet | State and vendor work side-by-side throughout process on same teams. The contract is staff augmentation. State manages all groups and approves all phases. |
| Data needs in test databases? | Unit/System/Regression
- Test database with test data. UAT/QA - Production volume test environments to validate performance & real-life scenario testing. |
Create
test data by entering intake cases and following through the life of the
case. |
Created clean data for testing. | Created mock production database with 1400 users defined. | Maintain separate testing databases with data created manually and maintained for several years. Have ability to download specific cases from production to test special features or problems. |
| When, where & how is converted data used in testing? | In initial development, conversion data is used for UAT/QA and performance testing. | Export production data to test when high volume is needed for load testing. | Did not use converted data for testing, but wishes they had. Had problems with bad data after implementation. | Converted data used in "dry runs" in each county to shake out defects prior to implementation. | Data is converted from a test database of old system to test database of new system. Production data is not used in test databases except case-by-case. |
| How do end-users participate in requirements development and testing? | Counties participate in RFP development, requirements validation, design, UAT, conversion testing, statewide users' group ongoing. | County users help test prior to piloting all major releases. For fiscal project, County fiscal staff assisted throughout design, requirements and testing. Project was very successful. | Users have cooperated in the design phase, but not in UAT. They don't see the benefit or have the time. | Set expectation early in project that end-users would participate. They assisted through requirements gathering and UAT. Problem was travel back for UAT. | End-users are involved throughout requirements and design process for new development. They assist in UAT from their own locations. Central office requests volunteers for major releases or highly specialized areas. |