Automated Testing QA
Implementation Plan
Ø
Initial Selection of QAers
o Four QAers from different teams
o Qualifications
§ Very interested in working with automated testing
§ At least one programming course or a familiarity with programming concepts
§ Has strong team leader support to devote 8 hours/week to development of scripts
§ Not essential that they are experts in their program
§ Problem-solver
§ Willing to help improve the process for using automated testing at Epic
o Demo automated testing program and discuss project with candidates to ensure a good fit
o Decide on four QAers
Ø
Training
o Assign a mentor from Fellowship (see Support Structure)
§ Help setup automated testing image
§ Act as primary support person
o Intro Class
§ Half hour
§ Cover basics of automated testing (PowerPoint)
§ Basics of automated testing software (PowerPoint)
§ Give Introduction to automated testing training guide
§ Set deadline for finishing exercises
o Automated Testing Training
§ Vendor Training – Introduction to Automated Testing
§ Self-exercises in vendor training book
§ Meet with mentor every couple days to answer questions
o Automated Testing & Epic software
§ Self-exercises with automated testing program and Epic programs
§ Include exercises that cover each trainee’s main area of focus
§ Meet with mentor every couple days to answer questions
o Show where Reference Material is located
§ Website – links to documents
Ø
Initial Project
o
Work with TL and
§ Decide based on needs of application
· Basic Workflow Tests – add on specific functionality tests
· Specific area of functionality – link together for workflow test
§ Use Automated Testing Guidelines doc to help decide
§ Ultimate Goal: Complete Workflow Automation
o Set checkpoints and deadlines for development of scripts
Ø
Support Structure
o “Fellowship of Automated Testing”
§ Main Support Group for QA
§ Fellowship will pass on issues to developers or if needed to vendor
§ Each new QAer will have a specific mentor from this group
o Email List for help
§ Email will go to all mentors
§ Problems/Resolutions document
· Filled in by person answering the question
· Field in document if problem/resolution should be added to reference guide
o “Wish-List” Document
§ Add in functionality/features/functions that QAers would like – mentors review and decide what would be good to look into, prioritize custom functions needed, etc
o Support Documents
§ Setup Guide
§ Automated Testing & Epic software Reference Guide
§ Trouble-Shooting Guide (I have this issue > here’s the solution)
§ Automated Testing Guidelines – guidelines for what should/shouldn’t be automated
o Programmer Quality Assurance
§ Review by mentor of scripts
o Code Review
§ Occasional meetings to review code for new tricks/coding methods
o Organizational Meeting
§ Bi-weekly meetings to present what each person has done
§ Discuss problems/wish-list for functionality
o Functionality Ownership
§ Fellowship Controls most shared functionality
· GUI Map – document to record all changes made
· Custom Functions – document to record all changes made
· Facility settings in Automated Testing Env – document to record all changes made
Ø
Develop System to Run Scripts on a Timed
Basis and Record Results
o Develop a procedure to run the developed scripts at a routine time/date
§ Develop master driver script to kick off scripts
§ Have one or multiple driver scripts per application
o Develop a procedure to record/store the results of the scripts
§ Excel spreadsheet to track results and run reports
o Develop a procedure to look into errors/problems in the scripts and find out if they are a problem in the application or the script
Ø
Issues to Resolve Before Rolling Out