Test Automation Life Cycle
Following are the phases of Test Automation Life Cycle. It can
be varied from project to project.
1.
Automation Feasibility Analysis
1.1.
Decision to Automate Test
1.2.
Overcoming False Expectations for
Automated Testing
2.
Test Strategy
3.
Environment Set up
4.
Test Script Development
5.
Test Script Execution
6.
Test Result Generation and Analysis
1. Automation Feasibility Analysis
Before
kicking off implementing test automation, it is mandatory to analyze the
feasibility of the application under test (AUT). Whether AUT is a right
candidate or not for the test automation?
1.1 Decision to Automate Test
In this phase it is important for the test team to
manage automated testing expectations and to outline the potential benefits of
automated testing when implemented correctly. A test tool proposal needs to be
outlined, which will be helpful in acquiring management support.
1.2 Overcoming False Expectations for Automated Testing
Automated testing is valuable and can produce a
return on investment, there isn't always an immediate payback on investment.
Some myths regarding automation testing should be
cleared. People often see test automation as a silver bullet, but they have to
understand that test automation requires a significant investment of time and
energy to achieve a long-term return on investment (ROI) of faster and cheaper
regression testing. Automation testing should
be introduced correctly into a project to manage the valid expectations.
Also,
feasibility analysis should be done on the manual test case pack which enables
automation engineers to design the test scripts.
Following
are the feasibility check to be done to begin test automation:
- AUT automation feasibility
- Test Case automation feasibility
- Tool feasibility
1.3 Proof of Concept phase (POC)
Objective of this phase
is to do POC for customer after customer is identified as a lead.
Activities –
•
Identification and evaluation of test automation tool.
•
Identification of FW and changes as needed.
•
POC / Test cases development and scripting to be done as needed by the
customer.
•
Typically this takes 1 weeks’ time.
•
Arrange a demo for the customer.
•
There is no guarantee that the project will come to.
Deliverables
•
POC done.
•
Demo to customer.
2. Test Strategy
This
phase defines how to approach and accomplish the mission. First in test
strategy is selection of test automation framework.
Following
are the types of test automation framework:
- Record and Playback Framework
- Functional Decomposition Framework
- Keyword/Table Driven Framework
- Data Driven Framework
- Hybrid Framework
Other
factors which involves in test strategy as follows
- Schedule
- Number of resources
- Mode of communication process
- Defining in-scope and out-of-scope
- Return on Investment analysis
3. Environment Set up
It
is ideal to execute test automation scripts in regression environment. Test
environment set up phase has following tasks:
- Sufficient tool licenses
- Sufficient add-ins licenses
- Sufficient utilities like comparison tools, advance text editors etc.
- Implementation of automation framework
- AUT access and valid credentials
4. Test Script Development
Activities
of Automation test engineers are as follow:
- Object Identification
- Creating Function Libraries
- Building the scripts
- Unit testing the scripts
- Test execution
5. Test Script Execution
Following
are the tasks involved with test script execution team.
- Test script execution
- Defect Logging
- Modifying scripts as developer changes occur
6. Test Result Generation and Analysis
Result
generation and analysis is the last phase and important deliverables in test
automation. Results must be base lined and signed-off. Following are the
important activities in this phase:
- Result analysis
- Report generation
- Documenting the issues and knowledge gained
- Preparation of client presentation
No comments:
Post a Comment