VA RFI: Testing Support for VistA

Notice ID 36C10B23Q0528

The Contractor shall develop a Test Plan, which will outline the strategy, scope, approach, and schedule for testing activities. It will include details on testing objectives, criteria for success, test environments, resources required, test data, and methodologies to be employed. The Contractor shall conduct software testing and evaluation in support of all sustainment releases in accordance with VA software release standard operating procedures. The Contractor shall perform testing of VA-approved version releases and Adhocs for the DBMS IRIS for Health software with respect to the VistA platform. Software testing shall comply with VHA mandated Software Testing Requirements as defined in VA Process Asset Library for VA user acceptance testing and shall be automated where possible. Currently, the VistA operating environment consists of Virtual Machines (VM) running Red Hat Enterprise Linux (RHEL) and InterSystems Corp. (ISC) IRIS for Health DBMS. These VMs are located in both VA data centers and the Amazon Web Services (AWS) instance of the VA Enterprise Cloud (VAEC) environment. VA’s production environment is constantly evolving, and it is expected that the Contractor shall coordinate with VA as to the specific versions of operating system, DBMS, and relevant utilities. The Contractor shall maintain a testing environment that complies with all VA configuration requirements. At minimum, the Contractor shall conduct the following testing: 1. Unit Testing – of individual units of source code to determine if they are fit for use. 2. Integration Testing – of modules which are combined and tested as a group. The Contractor shall perform integration testing to ensure code maintenance activities do not affect the following dependent interfacing systems. 3. Regression Testing – against all previous test cases and results to ensure that new code, functionality, or new releases have not introduced errors to existing functionality.

More here.

🔊 Listen to Story