Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Automation Process, Maintenance & Responsibility
Transcript of Automation Process, Maintenance & Responsibility
Till date 10 major Content Collection Applications are automated .
Automation Test Coverage is almost 70% for every AUT and it signifies the prominence of Automation Test Scripts
Effective Process is defined to complete all these projects. It starts with Projects Prioritization and ends with User-Sign off.
Project Cycle & Usage of Automation Scripts
Automation Maintenance & Responsibility
Efforts of Virtual Team
To ensure continuous Maintenance of Automation Scripts, Bugs will be identified through out the Release during Build Validation, Ad- Hoc Requirements and Regression Test Phase
A bench mark is laid on Script Health/Stability that makes it eligible for Regression test phase
Bugs/Enhancements Identified through-out the process would be prioritized for next release and thus the process attains reliability
Automation Projects Prioritization
As a First Step Automation Requirements are gathered from Sub Teams.
Specific Metrics are defined to calculate the Priority of Automation Projects.Let's see all the Project metrics
Functionality Analysis by Manual Testing
End Testing, Code Reviews, Svn & QC Repository Management
To provide enough knowledge on “QTP functionality, Automation Framework and Test Scripts of Content Collection Applications” to Sub Team QA
Main Objective of the Project is to make Sub Team QA’s self-reliable of Execution and Complete Maintenance of Respective Automation Test Scripts.
QTP and Its Basic Functionaliies
QTP, Its Basic components and functionality
Content Collection Automation(High Level Details)
Overview on Automation Framework(Brief on Framework Components, Various frameworks used till date)
Code Walk Through of Generic Master Scripts, Common Libraries etc.
(Detailed explanation on mapping of all framework components to Test, Test case Execution Flow)
Framework Set Up in Work Machines(SVN Repository, Pre-defined settings, Environment variables and other dependencies)
Debugging Approach and Resolving Issues
Sub-Team Specific KT Agenda
Project Status(Framework in use, Stability, Test Coverage, Dependencies)
Overview on Test Scenario, Object Repository
Brief Code Walk through of Specific Application Library
Go Abouts and current status of the Project(Bugs/Enhancements)
Quality Center and Auto Triggering System
Quality Center, Its sync with Automation(QC major components, functionalities)
QC Repository, QC Automation Framework and Script Execution from QC
(Storing Automation Resources in QC, Manipulating them and Using them for Execution)
Auto Triggering System(ATS) and its interaction with QC
Effective Usage of Automation Scripts using ATS(Process followed during Build Validation, Regression Phase)
Script Acquaintance was a given priority and many hands-on exercises and practical exercises helped us in this context
Code Walk- Throughs
Setting up of Automation Environment
Understanding Health Of Project &Previous Test Results Analysis(Individual Sessions)
Kick Start Sessions For Bug-Fixing
Regression testing through ATS
Sub Team QA's had proactive approach through- out this project.
Active Participation during Regression Test phase
Identified Valid Test Case Failures
Mastered with the Execution Flow of Master/Driver Script that gave them a great edge in debugging Script Issues
Scrutinized the Application Functionality and came up with discrete list of Bugs/Enhancements that would have direct impact on Automation Script Stability
Road Map Ahead
Objective of this Project is successfully achieved and Automation team will extend its support in coming releases to establish effective and reliable process
Plan of Phase 2 would be decided at the end of release based on feed back of respective sub team members
On A Bigger Picture, our vision is to make Automation testing a Key factor in the process of Continuous Integration
Efforts of the team signifies the accomplishment of this Project Objective in a grand manner
Responsibility of Automation Script Maintenance is now held by respective Sub Teams and this strengthens the Automation process
Usage Of Automation Scripts
Build Validation (Continuous Integration)