Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Automation Life Cycle

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 11

Automation Test Life Cycle

Requirement Analysis(input
manual test case)

Tools selection

POC (proof of concepts)


Customer Approval

Automation Test Plan

Segregate automatable/ non


automatable test case

Framework development

Test scripts development

Peer Review

Test Data Preparation

Test scripts Execution

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

Segregate automatable/ non automatable test case

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.

1. Create frame folder structure


2. Automation environment set up
3. Create generic scripts
4. Create driver scripts
5. Test data template
6. Automation report template
7. configure with Test management tools and others open source tool like (Review board
and CI tool , Ant , Code coverage tol etc.)

Test scripts development

1. Actual Test scripts development along with project specific methods

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

1. Review the logic of the code


Automation Test Life Cycle

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

Test scripts Execution

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

 Can be executed from ant or from the command line.


Automation Test Life Cycle

 Instruments Java bytecode after it has been compiled.


 Can generate reports in HTML or XML.
 Shows the percentage of lines and branches covered for each class, each package, and
for the overall project.
 Can sort HTML results by class name, percent of lines covered, percent of branches
covered, etc. And can sort in ascending or decending order.

<property file="build.properties" />

<path id="cobertura.classpath">
<fileset dir="${cobertura.dir}">
<include name="cobertura.jar" />
<include name="lib/**/*.jar" />
</fileset>
</path>
Automation Test Life Cycle

What can Jenkins do?

Jenkins is a build monitoring tool , which is used to continuously monitor

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.

 Generate test reports


 Integrate with many different Version Control Systems
 monitor the svn build system
 Automatic Email notification of test report
 Schedule the batch execution
 Automated test suites are run
Automation Test Life Cycle

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:

 Enables simultaneous running of tests in multiple browsers and environments.


 Saves time enormously.
 Cross browser testing
 Utilizes the hub-and-nodes concept. The hub acts as a central source of Selenium
commands to each node connected to it.
Automation Test Life Cycle

SVN

Subversion is a free/open source version. and its used to manages files and directories, and the
changes made to them, over time.

This allows you to recover older versions of your data

or examine the history of how your data changed.

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

provide remote access

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;

public class SampleLog {

public static void main(String[] args) {

Logger log = Logger.getLogger(SampleLog.class);


Automation Test Life Cycle

Properties properties = new Properties();

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.Console.layout.ConversionPattern", "%-4r [%d] [%-5p] [%c %x] - %m


%n");

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");

properties.put("log4j.appender.File.layout.ConversionPattern","%-4r [%d] [%-5p] [%c %x] - %m%n");

PropertyConfigurator.configure(properties);

log.info("login is sucesfull");

log.error("login failed");

log.warn(" phone is not displayed");

log.debug("stop the exection for debug");

}
Automation Test Life Cycle

You might also like