Automation Life Cycle
Automation Life Cycle
Automation Life Cycle
Requirement Analysis(input
manual test case)
Tools selection
Framework development
Peer Review
Result generation
Scripts Maintenance
Automation Test Life Cycle
Requirement analysis : Understanding of manual test case & functionality of the application ,
Regression test scenario are identified for the each scenario releases.
Tools Selection : Select the suitable tools which support to AUT , and take End 2 –End test case
and create POC , just to ensure that automation can be done for the application .
Proof of concept : To check the tool feasibility ,and helps to customer demo , and also check of
the automation support for the AUT
Automation Test Plan : A test automation plan shall be documented each releases of xyz
application, this document will covers the test automation activity for the release , the test
automation plan consist
1. Objective
2. Scope of testing
3. Automation Methodoogy
a. Planing
b. Automaton
c. Execution
d. DashBoard reporting
e. Script execution and Maintenance
5. Test Environment
6. Acceptance Criteria
7. Test Deliverables
8. Change management processes
9. Quality management process
10. Test defectmanagement
Automation Test Life Cycle
Regression tese case are identified and categorized in to 2 categories Automatable / non
automatable,
And it is send it customer review.
FrameWork development
Chose suitable automation framework and developing the main driver scripts , sub scripts ,
utility , and common libraries function, logger function etc.
Peer Review :
Validate the test scripts before storing in the CI Repository , Proper debugging of the scripts will
be done to rectify the error in the scripts , these errors will be corrected by peer review
2. code coverage
3. Test data should not be hardcoded
4. Remove all unused variable
5. Check the naming convention as per the coding standards
6. Automation scripts should identified the Bugs
7. Check the reusability factors , is its require create a separate libraries
8. Proper test step comments j
9. Test case description with Author
The test execution phase will be involved executing the identified the test scripts in the
automation framework , and the details execution report can be send to Costumer .
What is Cobertura?
Cobertura is a free Java tool that calculates the percentage of code accessed by tests. It can be
used to identify which parts of your Java program are lacking test coverage. It is based on
jcoverage.
Features
<path id="cobertura.classpath">
<fileset dir="${cobertura.dir}">
<include name="cobertura.jar" />
<include name="lib/**/*.jar" />
</fileset>
</path>
Automation Test Life Cycle
The build system (svn) , where members of a team integrate their work frequently. Each
integration is verified by an automated build (including test) to detect integration , errors as
quickly as possible , and send email to team members , in case od build failure.
Selenium Grid
Selenium Grid is a tool used to run parallel tests across different machines and different
browsers all at the same time. Parallel execution means running multiple tests at once with
different browser.
Selenium grid are used to run the test scripts in remote machine
Features:
SVN
Subversion is a free/open source version. and its used to manages files and directories, and the
changes made to them, over time.
SVN Usage
Automation Developers use Subversion to maintain current and historical versions of files,such
as source code
Tracking changes
provide backup
provide merging
centralizes repository shared network , but contolling access to files between team memebers
Svn
http://sourceforge.net/projects/tortoisesvn/
http://www.visualsvn.com/server/download/
LOG 4J
Automation Test Life Cycle
http://selftechy.com/2011/05/23/selenium-logging-with-log4j
If we are executing Test Suite with hundreds of automated test cases then logging all the events might
be useful.
With log4j it is possible to enable logging at the runtime with different style of information.
Log4j is built with three main concepts: loggers, appenders, and layouts. Logger is the main engine
which sends the logging requests to appender. Appender might be a console, a log file, printer, etc.
Layout is the formatting of the log output
package pac;
import java.util.Properties;
import org.apache.log4j.BasicConfigurator;
import org.apache.log4j.Logger;
import org.apache.log4j.PropertyConfigurator;
properties.put("log4j.rootLogger", "INFO,Console,File");
properties.put("log4j.appender.Console", "org.apache.log4j.ConsoleAppender");
properties.put("log4j.appender.Console.layout", "org.apache.log4j.PatternLayout");
properties.put("log4j.appender.File", "org.apache.log4j.FileAppender");
properties.put("log4j.appender.File.file","logs/ActitimeLog.log");
properties.put("log4j.appender.File.layout","org.apache.log4j.PatternLayout");
PropertyConfigurator.configure(properties);
log.info("login is sucesfull");
log.error("login failed");
}
Automation Test Life Cycle