Automated Testing Implementation Plan

Dec 2002

 

Phase 1 – Proof of Concept & Vendor Selection

After evaluating 12 vendors, two were initially selected for onsite proofs of concept.  During the proof of concept, each vendor attempted to identify controls and write basic test scripts with Epic.  However, neither performed particularly well with Epic software.  The third choice of the evaluation group was invited onsite for a proof of concept.  They performed best with Epic, and left the evaluation group with the best impression.

 

 

 

Phase 2 – Pilot Project

This phase will last approximately 3-4 months, and accomplish a wide variety of goals.  Two concurrent licenses will be purchased during this phase, along with a week of onsite training and support.  These licenses will be used to verify the viability of automated testing with Epic Software, and to also generate a return on the initial investment of money and time in this project.

 

During this phase, a QA Process Planning Group will be formed.  This group will be made up of 5-6 QAers representing the different applications.  We estimate the time commitment to be approximately 10 hours a week, although this will be flexible based on deadlines and company commitments. 

 

The goals for this group during Phase II are as follows:

  1. Determine what has to be done to build an Epic script library and develop time estimates for completing these libraries for each application.
  2. Work with Software Test Developers to develop standards for coding
  3. Learn some functionality and develop some basic test scripts
  4. Outline a plan for Phase 3 to rollout automated testing to QA

 

 

 

Phase 3 – Rollout to QA

If it has been determined that automated testing will be beneficial to QA, the Process Planning Group will put into action the plan that was developed during Phase 2 to roll out automated testing to the QA teams.  This phase will be approximately 15 to 18 months, based in part on the experiences in Phase 2.  The current plan would be to have a scripter for each application that would work with others on the team to record scripts.  The team representative on the Process Planning Group, who would work with the software test developers to tweak the scripts for repetition, would coordinate this.  Script libraries for each application will be developed, for use in CD, regression, and migration testing.