automation 2.0: shaping the future of test automation

Automation 2.0

Automation Trends and Progress

August 6, 2013

2 ©Alliance Global Services 2013

Focused on Outcomes We understand the importance of release dates,

software quality and the impact of bugs on client

satisfaction and support – we are successful only

when our client’s end customers are successful.

Disciplined and Experienced We leverage the best practices from commercial

software product development including

extensibility, reliability and maintainability from the

start. We measure twice, cut once and plan for

the future.

Reliable We provide delivery assurance with Output

Certainty (we deliver what we promise) and

Traceability (business acceptance criteria for all

user stories).

A Jack of All Trades We are not a generalist IT Services firm. Unlike

many of the large firms who are focused on IT, we

are focused on Product Development & Testing –

not IT. We develop, test and support our clients’

core products and platforms.

Too Big A multi-billion $ firm that only pays attention to

customers that spend more than $5M/year

Too Small A boutique firm that lacks process maturity and

scalability

We are: We are not:


Today’s Presenter

Presenter Srinivas Rao Labhani, Head of the Testing Solutions

Group, has more than 15 years’ experience in product testing,

enterprise applications testing, automation framework

development and test assessments. He has been instrumental in

defining Alliance's ScriptLess Automation Framework and is

involved in defining testing methodology for test automation and

managed testing services.

Today’s Host

As Director of Marketing, Sharon Lee heads the marketing

strategy and brand messaging for Alliance. With over

12 years of experience in digital and traditional marketing, she is

focused on the effective use of media for compelling brand

messaging and creating successful marketing programs with

measurable results that impact revenue. Sharon holds a B.A.

from the University of Pennsylvania.


Impediments in Achieving Best in Class Automation

Results

Lack of defined business objective

Not defining the business objectives

quantitatively

Not having the right automation strategy for identification of right candidates, tools, environment needs etc…

Not identifying the tool based on the needs of automation like: Functional GUI testing, Back-end, API Based, etc…

Not having the required skillset with-in to develop and maintain the automation scripts

Not identifying the right framework to be used for automating.


Trends of Automation

The so-called first generation of automated test tools consisted of record and playback

tools

The second generation of automated test tools supported data-driven,

i.e., capable of running scripts with multiple data sets.

The third generation of automated test tools supported

data driven, modular, i.e., capable of supporting

functional calls approach.

The fourth generation of automated test

tools supported data driven, modular,

keyword and combo of all

Defining test cases in simple

English-like language without

writing lines of code.


Features of a Robust Automation Framework

Efficiency

•Executes consistently across runs

•End-to-end automation, not just UI interfaces

•Modular design

•Easy to use tests for automation development

Cost

• Scriptless based design and English-like keywords for a faster automation script development

• Functional testers and BAs with application expertise to maintain and execute automation scripts

Speed

• Allows in-sprint automation for Agile projects

• Out of box integration with common Continuous BI tools

• Visual reporting and notifications to quickly identify cause of failures

Maintainability

• Readable scripts rather than programming

• Reusable test scripts

• Abstracted UI identifiers

• Data driven

• Visual logging


What is Model Based Testing?

Model-based testing is application of Model based design for designing and optionally also executing artifacts to perform software testing. Models can be used to represent the desired behavior of a System Under Test (SUT), or to represent testing strategies and a test environment.


Model Based Testing in Automation

Model-based automated testing in which test cases

are generated from a model, that describes (usually

functional) aspects of the Application Under Test

(AUT).

• In the model based automation we can

– Design use case flow by:

• Designing the flows (Happy Path and Alternate paths)

– Designing each steps

– Verification points

– Capability to automate at the atom level of the test script.

– Generates test case document and traceability matrix.

– When model changes because of behavioral changes, tests also will change with minimal effort.


Why Model Based Testing in Automation?

Why Model Based

Testing?

Common View for

Manual and Automated

Tests Automation

at Atom Level

High Potential of

Re-use

Easy to Design

Lower Maintenance

Increased Coverage

Why Model Based Testing? • Common View

• A graphical representation of the test cases by dragging and dropping of the components.

• Automation at Atom Level • Each components of the automation model can be

created, associate objects, define the data and action against the component.

• Re-Use • Due to higher level of modularity, the re-use of the

automation model at Atom Level enables higher re-usability

• Easy To Use & Lower Maintenance • Automated tests can be created by dragging and

dropping. Thus enabling Business Analysts or Test Analysts to create and maintain without programming skill and not just by test automation specialists.

• Increased Coverage • Based on the well-defined models, the system

requirement test coverage can be easily measured while automation is provided to support scenario analysis and prioritization


Alliance Way of Model Based Testing in Automation

• Use diagrams to represent

words, ideas, tasks or other

items linked to and arranged

around a central key word or

idea.

– Use specific diagrams of

certain actions

Like: For actions use

Rectangle, Verification points

use Rounded Rectangle, Flags

to indicate the positive and

negative flows, etc.

• Add the automation components association of Objects, Step Generator, Data at the Model/Component level


Model Based Automation Implementation Example

Lets consider ‘Add to Cart’ scenario of Amazon with log in and without login

• --- > indicates a single test case flow.

• Prioritizing test case

• Happy Path Test case Error Path (Negative Test case)


Automation – Model Based Automation


Thank You www.allianceglobalservices.com

[email protected]

http://www.allianceglobalservices.com/

automation 2.0: shaping the future of test automation

Technology