For more info visit: http://www.zentestlabs.com/
http://blog.zentestlabs.com/
--Manual vs. Automated Testing
--Key Challenges and their Business Impact
--Zen Test Labs Test Automation Solution
--ZenFLOW- Zen Test Labs’ Proprietary Test Automation Implementation Methodology
--Automation Tools vs. Automation Frameworks
--Zen Test Labs Unique Offerings in Test Automation
--Zen Test Labs Test Automation Experience
--Why Zen Test Labs?
--Case Study 1- Test Automation for a Software Product Company
--Case Study 2- Test Automation in an Agile Environment
2. TABLE OF CONTENTS
Manual Vs. Automated Testing
Key Challenges and their Business Impact
Zen Test Labs Test Automation Solution
ZenFLOW- Zen Test Labs’ Proprietary Test Automation Implementation Methodology
Automation tools vs. Automation frameworks
Zen Test Labs Unique Offerings in Test Automation
Zen Test Labs Test Automation Experience
Why Zen Test Labs?
Case Study 1- Test Automation for a Software Product Company
Case Study 2- Test Automation in an Agile Environment
2
3. MANUAL VS.AUTOMATED TESTING
3
Feature Manual Testing Automated Testing
Test Case Creation The test case creation effort is lesser than
automation.
Creating the automation scripts can be
time consuming but is typically a one
time activity. Once the scripts are
created they can be reused multiple
times over.
Test Case Execution Time consuming and tedious: Since test cases
are executed by human resources thus it is
very slow and tedious.
Automation dramatically reduces the
test case execution time. This is due to
the fact that scripts directly call
application and test.
Test Reporting & Management All reporting is manual and dependent on
testers for accurate reporting.
All reporting and management is
automated thus giving an automated
view of all testing activity
Maintenance There is no concept of seamless maintenance
as all test cases have to be manually updated
each time there is a change
If the automation design is right, then it
facilitates seamless maintenance by
enabling users to make changes at the
function level to update all scripts
associated with that function
Fit Manual testing is best suited for an
environment where the application is small
(lesser number of screens) thus making the
test case count small. It also is a better fit
where testing is not repetitive.
Automated testing is best suited for
applications that are large (more number
of screens) and where testing is
repetitive (frequent regression cycles). It
is not suitable if application is not stable
4. TYPICAL CUSTOMER CHALLENGES AND BUSINESS IMPACT
4
Common Challenges
• Many automation projects either do not
begin at all or loose sight midway
• ROI not realized for most automation
projects
• Lack of availability of skilled resources
• Automation solutions implemented are not
extensible, maintainable and scalable
• Feasibility testing done prior to automation
does not always paint a true picture resulting
in effort overruns
Business Impact
• Projects abandoned abruptly resulting in
high sunk cost
• Delayed “Time to Market” caused due to
unfulfilled expectations from automation
projects
• Increased cost (of maintaining the test
assets)
• Delays in releases, employee burnout,
increased cost to retain critical resources
• Poor/ No ROI from automation projects
5. ZEN TEST LABS TEST AUTOMATION SOLUTION
5
AUTOMATION SERVICES
- Functional automation using
commercial/ open source tool like QTP/
Selenium, etc.
- Performance test automation using tools
like Load runner, etc.
- Integrate test automation with test
management tools like QC
ZENFRAME BASED
AUTOMATION
FRAMEWORK
DEVELOPMENT
SERVICES
- Test Automation Framework
development team that brings
experience of development frameworks
for multiple customers
- Development language agnostic
- Ability to adapt to customer design
principles
AUTOMATION STRATEGY
CONSULTING
- Functional Automation using Zen
Test Labs’ Proprietary Test
Automation Framework-
ZenFRAME that results in 33%
faster script creation and 40%
faster execution
- Best in Class approach developed
over hundreds of years of test
automation experience
- Tool agnostic
- Assess Automation
readiness
- Decide what to
automate
- Tools, frameworks for
automation
- Sourcing models
- Roadmap to realize ROI
6. ZENFLOW:ZEN TEST LABS’TEST AUTOMATION IMPLEMENTATION
METHODOLOGY
6
Phase One: Defining
OF: Objective Finding Defining Why To Automate
FF: Fact Finding Deciding When To Automate
PF: Problem Finding Finding Where the problem is
Phase Two: Scoping
TF: Tool Finding Identifying Which Tool to automate with
TCF: Test Case Finding Identifying What Test Cases to Automate
TDF: Test Data Finding Finalizing What Test Data to Automate with
Phase Three: Strategizing
SD: Solution
Designing
How to automate – Finalize design of
framework
SC: Solution Coding How to automate – Coding the scripts
AT: Acceptance
Testing
How to automate – Acceptance Testing
7. AUTOMATION TOOLS VS.AUTOMATION FRAMEWORKS
7
Feature Automation Tool Automation Framework
Test Case Creation Automation engineer who understands scripting
language of an automation tool like QTP/ Selenium,
etc. builds scripts that can be executed
Automation engineer who understands
scripting language of an automation tool like
QTP/ Selenium, etc. designs an overall
automation approach with scripts,
functions, test data and utilities
Test Case Execution Automation engineer executes scripts based on
test cycles required
Depending on the framework, SME’s/
business analysts/ testers can use the
automation framework to run test cycles as
per their need
Test Reporting & Management The automation engineer who runs the test cycles
typically reports on the results on the cycle.
Depending on the framework, the GUI
provided by the framework enables users to
directly access and share results
Maintenance An automation engineer has to change scripts and
functions based on the changes in the application
thus increasing the time taking to change and
dependency on that individual
Depending on the framework, only selected
functions can be modified once instead of
having to change all the tests when changes
occur in the product
Fit Direct scripting through a tool is ideal when the
application is not very large with low feature
updates.
Automation frameworks are ideal for any
automation project as they create an overall
design and approach for how automation
should happen with features such as GUI,
seamless maintenance, etc. depending on
the framework used
8. ZENFRAME
8
APPLICATION UNDER TEST
AUTOMATION TOOL (COMMERCIAL: QTP OR
OPEN SOURCE: SELENIUM)
ZENFRAME AUTOMATION FRAMEWORK
TEST MANAGEMENT
TOOL
(COMMERCIAL: QC
OR OPEN SOURCE:
TEST LINK
OR ZENFRAME)
BUILD
FUNCTIONS
BUILD SCENARIOS
BUILD TEST CASES
BUILD TEST DATA
EXPECTED VALUES
CALL
FUNCTIONS
EXECUTE
REPORT &
MANAGE
9. 9
RIA
REMEDIATION INCLUDED
AUTOMATION
CIA
CHANGE INCLUDED
AUTOMATION
PIA
PAYMENT INSURED
AUTOMATION
• Outcome based ‘Pay As You Save’ pricing
model
• Delivery of automation scripts on minimal
upfront payment
• Pay remaining as you realize ROI of
automation over manual testing
• Useful model when management buy-in
for automation is low
• Remediation of
manual tests
followed by
automation
• One price quote for
improving,
structuring manual
test cases prior to
automation
• Useful when manual
tests are not well
written
• Automation followed by
maintenance to handle
any changes in the
application
• One price quote that
includes automation as
well as any subsequent
automation in the next
year
• Useful when application
is expecting changes
and is not being fully
revamped
Flexible
Models
ZEN TEST LABS UNIQUE OFFERINGSIN TEST AUTOMATION
10. ZEN TEST LABS’ TEST AUTOMATION EXPERIENCE
Manual and Automated Testing Front to Back for a leading banking software provider
from the Middle East for its core banking system
End to end testing (including test automation) for a leading Milwaukee, USA based bank
for their web based Treasury Online Solution
Test automation on the cloud for a US based leading e-gift card services provider
Manual and Automated UAT of a web based treasury management solution at the
American subsidiary of a large Canadian Bank
End to end test case automation for a leading corporate banking product company
Test Automation consulting and strategy roadmap for one of the world’s largest banks
Automation of test cases for a leading cash management product company
Consulting for a leading enterprise software company on “How to improve their flagship
Test Management product?”
10
11. WHY ZEN TEST LABS
11
NICHE FOCUS
•DOMAIN EXPERTISE
(BANKING- TREASURY MGMT.,
CASH MGMT., ETC.)
•FUNCTIONAL KNOWLEDGE (APP.
EXPERTISE- ACI-S1, FUNDTECH, FIS,
CORE BANKING SYSTEMS, ETC.)
•QA FOCUSSED
METHODS
•TEST CASE DESIGN MIND-SET
(WHAT TO TEST, HOW TO TEST,
ETC.)
•OPTIMIZATION MINDSET (RISK
BASED TESTING)
•RIGHT MEASUREMENT
MINDSET (HOW MUCH TO TEST
TOOLS & UTILITIES
•PROPRIETARY AUTOMATION
FRAMEWORKS (ZENFRAME,
ZENBA, ETC.)
•DOMAIN ACCELERATORS (TREASURY
MANAGEMENT)
•DATA MIGRATION UTILITIES
(REDUCED TIME WITHOUT COMPROMISING
ON THE QUALITY OF VERIFICATION .
MINIMAL TO NO IMPACT OF RAMP UP-
GIVEN THE RUNWAY ISSUES)
REDUCE RISK, IMPROVE
COVERAGE
NEW PRODUCT
IMPLEMENTATIONS
DRAMATIC
REDUCTION IN QA
TIME AND COST
(ESPECIALLY IN
REPETITIVE TESTING
LIKE REGRESSION)
ENABLE BA’S TO TEST
SEAMLESSLY
GUARANTEED ROI ON
AUTOMATION
BALANCE TIME TO
MARKET, COST AND
RISK
IMPROVED MANUAL
AND AUTOMATED
TESTING EFFICIENCY
12. CASE STUDY 1–TEST AUTOMATION FOR A SOFTWARE PRODUCT COMPANY
Our Solution
Zen Test Labs implemented its unique approach
to automation tool evaluation wherein different
classes of objects were verified for compatibility
instead of just a sample selection. Additionally,
automation design was feature driven instead of
being test case driven thus resulting in more
automation coverage
Methodology
•Zen Test Labs setup the testing process after
monitoring the past failures.
•Our team created a new test Automation
framework on the design principles of ZenFRAME
• Zen Test Labs automated the suite of 500 macro
business level scenarios executed 4 hours
The Client
The client is a leading provider of software products and services to banks of all
sizes around the world. They have over 1,000 clients worldwide, with 50 of the
worlds' leading banks across EMEA, The Americas, and Asia-Pacific. They develop
transaction banking solutions that automate activities such as payments, cash
management, settlement, liquidity management, and the financial supply chain.
Key Challenges
•Study the large repository of macro level business scenarios (800)
•Break down into micro level test cases for automation (2500-3500 test cases). Each
of the macro level business scenario had an average of 3-5 micro level test cases,
thus resulting in a total test case count of 2500-3500 test cases for automation
•Create a customized test automation framework to ensure 100% independence
from vendor
•Overcome past experiences of project failure by other teams and deliver
automation at a rapid pace
Key Results
•Automated the entire suite of 500 Macro level business scenarios (2500-3500 test cases) in 18 person months
•Created a customized test automation framework on the design principles of our proprietary test automation framework- ZenFRAME
•Achieved dramatic reduction in test execution time from 50 manual test cases a week to the entire suite of 500 (2500-3500 test cases)
being executed in 24 hours.
•Awarded Phase 2 project for automation of 300 macro level business scenarios (1000-1500 test cases)
•Delivered a 100% maintainable solution.
12
13. CASE STUDY 2– TEST AUTOMATION IN AN AGILE ENVIRONMENT
Our Solution
The client engaged Zen Test Labs for our offshore
functional automation testing service. As a part
of this engagement, Zen Test Labs also assisted
the client with automation of configuration
testing and went on to cover security testing and
software configuration management.
The Client
The client is leading provider of product development solutions
to global corporations. With a specialization in agile
development methodologies and web development, the client
delivers enterprise advantage to organizations requiring
technical excellence and business efficiency at a cost conscious
value.
Key Challenges
•No functional test cases present (only unit level test cases)
•Multiple daily code updates, fortnightly release cycle
•High TAT on Manual Testing- 2 days per cycle
•Multi browser setup demanded configuration testing
•High TAT on Manual Configuration Testing- 3 days per cycle
13
Business Situation and Impact
The client was engaged with a leading e-gift card
services provider to develop an application on
agile development methodologies.
With an average of 1 new update in the code
every day from the developers to testers and 1
release a fortnight to their client, manual testing
that took 2-3 days per cycle was not feasible.
We cut the test cycle time down to 1 .5 hours
and gave the development team complete
independence from testing
Methodology and Results…turn slide
14. CASE STUDY 2– TEST AUTOMATION IN AN AGILE ENVIRONMENT
14
Development & Test
Enviornment Study
• Development
enviornment study
• Macro level business
scenario study
• Desired output from
automation study
Test Automation script
creation
• Creation of 350+
functional test cases in
selenium
• Total effort of 45 days
using 1.5 resources
Continous Integration &
Multi browser testing
Creation of automated
script that triggers when
developer checks in code
Creation of automated
script that executes multi
browser configuration
testing
Automation Execution
• Automated suite of 350+
test cases executed in 45
minutes
• Multi browser
configuration testing
exectued as part of
automation cycle in 45
minutes
Key Results
•Wrote and automated 350+ functional test cases (40+ Macro level business scenarios) in an open source solution; i.e.,
Selenium
•Cut Manual testing time from 2 days to 45 minutes per cycle
•Included multi browser configuration testing in automation cycle.
•Cut Configuration testing time from 3 days to 45 minutes per cycle
•Cut overall testing time from 5 days to 1.5 hours
•Complete test independence for developers in a continuous integration mode
•Engagement scope increased to cover security testing and software configuration management
Project Execution Methodology