MEDICAL HOME NETWORK

TEST PLAN
Version <1.0> <04/29/2013>

Revised: 04/29/2013

MEDICAL HOME NETWORK

VERSION HISTORY
Version # 1.0 Implemented By Vinay Thota Revision Date <04/29/2013 > Approve d 1By <name> Approval Date <mm/dd/yy> Reason

The purpose of the test plan is to ensure that the current Accounts Payable Purchase Order (APPO) system on PeopleSoft 7 draft

UP Template Version: 04/29/2013

Revised: 04/29/2013

MEDICAL HOME NETWORK

1. Introduction............................................................................................................................................ 4 Medical Home Network unites public and private organizations in a partnership to improve the health status of people living on the South and Southwest Side of Chicago. Were a neutral third party dedicated to facilitating collaboration between organizations such as the State of Illinois Medicaid, South Side area hospitals, federally qualified health centers (FQHCs), and high-volume Medicaid private practices. The Medical Home Network model is designed to bring together these providers to be accountable for strengthening the health care delivery system and improving the health status of South and Southwest Side Chicago residents......................................................................................................4 2. Purpose................................................................................................................................................. 4 3.INTENDED AUDIENCE.......................................................................................................................... 4 4. Components.......................................................................................................................................... 4 8. Test Environment - Process Overview ...............................................................................................11 9. Tools.................................................................................................................................................... 11 10. Schedule .......................................................................................................................................... 13 11. Deliverables....................................................................................................................................... 13 12. Risks/Contingencies......................................................................................................................... 14 13. Assumptions...................................................................................................................................... 14 14. Test Plan Approval............................................................................................................................. 14

Revised: 04/29/2013

MEDICAL HOME NETWORK

1. Introduction
Medical Home Network unites public and private organizations in a partnership to improve the health status of people living on the South and Southwest Side of Chicago. Were a neutral third party dedicated to facilitating collaboration between organizations such as the State of Illinois Medicaid, South Side area hospitals, federally qualified health centers (FQHCs), and high-volume Medicaid private practices. The Medical Home Network model is designed to bring together these providers to be accountable for strengthening the health care delivery system and improving the health status of South and Southwest Side Chicago residents.
This document will outline the strategy and approach that will be used to test the MHN DW .

2. Purpose
The purpose of the test plan is to ensure data loaded from all the flat files through SSIS the MDH DW is thoroughly tested, resulting in a successful implementation of new and existing functionality, business processes, reports, interfaces.

3.INTENDED AUDIENCE
Medical Home Network organizes health care providers around a singular vision: to improve the health status of people living on Chicago's South and Southwest Side. Together, were working to enhance health care quality and access and to reduce the fragmentation and cost. Our current list of committed participants includes:

4. Components
The test plan consists of the following: A. Test B. Test C. Test D. Test E. Test Scope Items Strategy Approach Environment
4

Revised: 04/29/2013

MEDICAL HOME NETWORK

F. Test Tool G. Test Schedule H. Deliverables I. Risks/Contingencies J. Assumptions K. Approval

4.1 Test Scope

The scope of the work to be performed includes the following: Development and implementation of a strategic, or Master Test Plan (this document). Development and implementation of a testing approach based on best practices. Establishment and implementation of verifying and validating application(s) compliance with business requirements. Identification of all the resources required to support the project testing initiatives. Testing efforts focus on validating the integration of Eligibility. Testing efforts focus on validating the integration of Claim Detail. Testing efforts include validating integration of Pharmacy. Testing efforts include validating integration of Health Condition. Testing efforts include validating integration of ER Alerts. Testing efforts include validating integration of Last PCP Visit. Testing efforts include validating integration of Last Medication.

4.2 Test Items

Testing will consist of several phases; each phase may or may not include testing of one or more of the following items:
List of All Test Items Items To Be Tested

Integration of SNC to MHN DW Integration of IHC to MHN DW

Items Not To Be Tested

{Usability}

If not, why not

{No usability spec}

Revised: 04/29/2013

MEDICAL HOME NETWORK

Items Not To Be Tested
{Reliability} {White-box testing}

If not, why not

{No way to get meaningful uptime testing in QA} {No white-box resource on the test team}

Revised: 04/29/2013

MEDICAL HOME NETWORK

4.3. Test Strategy

Listed below are the various types of testing that will take place in four test phases.

Testing
Data Validation

Phase
1

Role
Developer, Tester

Description
Validating the data loaded from flat files to staging area. Developer testing to validate that new code can be executed to completion with no errors. To validate the application meets business requirements under various scenarios for a functional area. Measuring the time an activity or key process takes to complete. This testing should be done throughout

Examples

Unit Testing

Developer

Functional

Tester

Performance

1,2,3

Tester

Revised: 04/29/2013

MEDICAL HOME NETWORK

the test phases. CrossFunctional Process 2 Tester Crossfunctional process testing to validate the application works across functional areas or other applications Regression testing to validate whether the recent program or code change has not adversely affected existing features.

Regression Testing

Tester

4.4 Test Approach

The MHN DW Integration Phase 1.0 testing approach will include:

4.4.1 Unit Test

Applies to all application code, interface programs, database stored procedures, and other utility code. Objectives are to demonstrate that: Developers will perform manual unit testing. Individual developers are responsible for unit testing their code. Team leads and architects will review. Revised: 04/29/2013 8

MEDICAL HOME NETWORK

Development teams are responsible for spot-checking and enforcing practices and standards for coding and unit testing. Unit testing will take place continuously during construction. Unit test cases will be added whenever functionality is added, code is reorganized, or defects are fixed.

4.4.2 Smoke Test

Applies to code chunks or full code builds delivered from the Development Team. Objectives are to demonstrate that a build intended for further testing is correctly installed on the target test environment and is working as expected. Objectives do not include performance testing. Shakeout tests will be executed by the team(s) designated as the responsible party. Shakeout tests will be selected from a set of string or system test cases prior to the shakeout of a build in the test environment to focus on areas of anticipated vulnerability for the environment and code. Shakeout tests will be performed whenever a new build is installed in the Test, External Integration, Acceptance and Production environments. Shakeout tests will use a limited number of regression test scripts built during string or system testing to confirm proper operation of a build in the target environment.

System Test
System Test will include validation and verification of the followings but not limited to: Data Completeness. Ensures that all expected data is loaded. One of the most basic tests of data completeness is to verify that all expected data loads into the data warehouse. This includes validating that all records, all fields and the full contents of each field are loaded. Strategies that will be considered include: o o Comparing record counts between source data, data loaded to the warehouse and rejected records. Comparing unique values of key fields between source data and data loaded to the warehouse. This is a valuable technique that points out a variety of possible data errors without doing a full validation on all fields. Utilizing any data profiling tool that shows the range and value distributions of fields in a data set. This will be used during testing and in production to compare source and target data sets and point out any data anomalies from source systems that may be missed even when the data movement is correct. Populating the full contents of each field to validate that no truncation occurs at any step in the process. For example, if the source data field is a string (30) make sure to test it with 30 characters.

4.5 Test Environment

Revised: 04/29/2013 9

MEDICAL HOME NETWORK

TEST ENVIRONMENT
The build will be delivered to X environment.
Build and Deployment Process

The Project team receives email from the X team once the build had deployed.
Configuration Management

The LEAD is responsible and the details are beyond the scope of the tester.
Hardware Specification

The client machine that will be used to test the application runs Intel Core i5 - 3210M CPU @ 2.50GHz, 8 GB DDR2, 750 GB HDD and DVD R/W drive among others.

Software Specification

The project involves Microsoft SQL Server 2008, SSIS. The OS is Windows 8 for client machines and Windows Server 2008 for backend and servers. System Component Database Database Instance / Schema Database Database Instance / Schema Database Database Instance / Schema Windows Server 2008 SSIS Description

4.6 Test Tools and Techniques

The idea is to create expected results and then compare those with the actual results. The test team has a number of generic tools to accomplish this. In addition, a number of custom scripts will have to be developed to test project specific functionality like SSIS. The tools used primarily are SQL Server 2008, Application Lifecycle Management (ALM).

Revised: 04/29/2013

10

MEDICAL HOME NETWORK

8. Test Environment - Process Overview

Diagram was provided by

9. Tools
A. Test Director will be used by 1. Test coordinator to monitor test development, testing progress, and defect reporting.
Revised: 04/29/2013 11

MEDICAL HOME NETWORK

2. Test Designers to document tests. 3. Testers to run tests and report defects. 4. Developers to review and update defects. B. ------ will be used by SSIS to run the load tests

Revised: 04/29/2013

12

MEDICAL HOME NETWORK

10. Schedule Test Activities Create Master Test Plan Create Test Design Create Test Cases Phase 1 Testing Phase 2 Testing Phase 3 Testing Redevelop Automated Test Cases Create Customer Acceptance Criteria Phase 4 - Customer Acceptance Testing Start Date End Date

11. Deliverables
Deliverable Responsibility Completion Date

A. Master Test Plan B. Functional Area Test Plan C. Functional Area Test Design D. Functional Area Test Cases E. Phase 1 TestingCompleted F. Phase 2 TestingCompleted G. Redeveloped Automated Tests H. Phase 3 TestingCompleted I. Customer Acceptance Criteria J. Phase 4 TestingCompleted

Revised: 04/29/2013

13

MEDICAL HOME NETWORK

12. Risks/Contingencies 13. Assumptions 14. Test Plan Approval

By signing here, you are approving the test plan . Functional Project Managers ____________________________________________ __ Functional Project Lead ____________________________________________ __ Technical Project Lead ____________________________________________ __ Date Reviewed Date Reviewed Date Reviewed

Revised: 04/29/2013

14