Test Automation

1
Test Automation
Presentation by Venkata RadhaKrishna
2
Who Are We Independent Software Testing Company

• Headquartered in Hyderabad, India.
• Location throughput Pune, Mumbai, Bangalore
  Delhi
• Technology centers in Hyderabad Bangalore
• 115 testing professionals
• Rapidly growing and profitable
• Thatavarti is surname of our founder
• Sanskrit meaning of Thatavarti is Intelligence.

3
Agenda

• Software Testing Challenges Automation
  Context
• Test Automation Perspective
• Value Proposition
• Thatavarti Test Automation Process (TTAP)
• Test Automation Architecture
• Test Automation Demo
• Thatavarti Expertise

4
Software Testing Challenges Regression Testing

• Third Party Products
• Deployment Config
• Database
• Operating System
• Browser

Test Object

• Bug Fixes
• Minor Modifications
• New Functionality
• Integrations
• Service Packs
• Patches
• Interfaces

Test Environment
5
Software Testing Challenges Coping with
development
Development time
Version 1.0 5000 days
Version 2.0 2500 days
Version 3.0 2000 days
Test time
Version 1.0 5000 days
Version 2.0 1.0 2500 2500 days
Version 3.0 (2.0 1.0) 2000 1250 2000 days
Impact Analysis testing
6
Test Automation(TA) Perspective

• TA aims at improving the effectiveness and
  efficiency of the
• test process throughout system life cycle.
• TA helps in being able to test quickly
  consistently
• TA is not a good by itself, value addition to
  manual test
• TA demands a paradigm shift from
  tool-orientation to
• process orientation.
• TA is long term investment.

7
Test Automation Value Proposition

• Reduction in testing costs
• Un-attended
• repeatability
• Less machines Improved machine utilization
• QA engineers can focus on Kernel test activities
  
• Shortened test lead times
• Manual test effort reduction
• Better Speed in executing tests
• Re-usable test ware
• Monitoring QualityHealth of the product
• Insight about the risks Quickly
• Consistency across test runs
• Test frequently and thoroughly

8
Should I go for test test automation.. It depends

• Test effort levels
• Test Process maturity
• Organizational readiness
• Quality of documentation
• Quality of Test Documentation
• Knowledge levels of test automation
• Technical knowledge of the testing crew
• Business risks involved in not doing regression
  testing
• Stability,complexity and future plans of
  Application\Product

9
Thatavarti Test Automation Process (TTAP)
Objective Improving the effectiveness and
efficiency of the total Test Process by making
use of test automation. Strategy Analysis of
opportunities. Implementation of an architecture
for the test suite.
10
TTAP
Feasibility Study
Proof of Concept
Identify the Scenarios
Design/Record the Script
Modify the Test Script
Run the Test Script
Test Suite Maintenance
11
Feasibility Study
Test Related Feasibility Objective scope of
the test How much of application can be
automated Organization Related
Feasibility Possible investments and
Expectations Over all maturity of the
process Technology Feasibility Stability of
Application under test (AUT) Test tool
suitability
12
Proof of Concept (POC)
POC helps in understanding the reality of
Automation. 2 Major and critical test scenarios
will be selected and the same are automated in
terms of work flow and data flow. Result of
Automation is 100 re-usable scripts with
application and data integrity. POC will help
the client in understanding ROI of automation
efforts and experience the time saving and
capabilities of Thatavarti Test Automation
skills.
13
TTAP.
Identify the Scenarios All the End-End scenarios
will identified with data interactions for the
automation. This scenarios are like a business
flows. Design Record the scripts Design
Hierarchical directory structure, naming
conventions, coding standards, modular, single
point maintenance, error recovery, checkpoint,
logging, synchronization, and configuration
management The basic skeleton is achieved using
the tool and process is designed according to
business flow. Modify the test scripts Test
scripts will be modified with necessary GUI
check points, loops, conditions and
constraints. Run the test scripts Test scripts
are run with real-time data for all the
regression cycles.
14
TTAP
Test Suite Maintenance(TSM) TSM is fully
dependent of Test Architecture. Test
Architecture is friendly for incorporating the
new functionality, work flow and GUI changes.
15
Data tables
Test Architecture
Business Function 1
Business Function N
Generic Function 1
Business Function 2
Driver Script
Generic Function 2
Cleanup Scripts
Generic Function N
Object Repository
Log Files
Reports
16
Test Architecture
Driver Script Each test script is independent
of the other scripts. Driver script covers one
End-End business functionality, In the process it
will call necessary generic and business
functions. Business Functions Applications are
build to address the business needs, all such
functionalities are identified and will be
written as business functions Generic Functions
Functionalities that are developed to support
the business functionalities are identified and
will be written as generic functions.  
17
Test Architecture
Start up Script Initializes the test environment
related parameters. Data tables All the scripts
are 100 dynamic, no code are constants are used
in the script. All the data related items are
separated and maintained as data tables in Excel
/ MS access/ Oracle and SQL Server Object
repository All the GUI objects in the
application would be identified and saved in a
global Object Repository.
18
Test Architecture
Log files An independent user defined log file
is maintained for each test run, typically
contains header with information such as Log
type, timestamp, test number etc. that can be
filtered to extract specific details on a
particular test step. Clean-up scripts This
scripts are used to kill the necessary
connections, test objects and clean the data
tables. Test Results Tool generated test results
are maintained independently.
19
Test Architecture -- Features
Maintainability Test Automation Suites generally
undergo changes in the following areas         
Application Functionality          Application
User Interface          Automated Test
Scripts   To minimize the re-work effort, each
area of impact is effectively managed by adopting
one level of indirection, abstraction and
componentization of impacted areas.
20
Test Architecture Unique Point
What is unique in this Architecture?
In this architecture we have followed Object
Oriented design, All the set of functionalities
that cover the respective business scenario are
covered under one class and separate methods are
written for each specific micro functionality.
21
Test Architecture -- Features
Re-Usability The entire test suite architecture
is based on the best practices of
componentization. The test script logic is
built/assembled by two major components         
Generic Functions Business Functions
22
Test Architecture -- Features
Portability Test Suite portability is built
around three aspects 1. Easily deployable in
different client environments         No hard
coded path strings used   2. Configurable test
environment settings      Configurable
environment settings using INI/ Config.xml
files   3. Integration with test harness tools or
work as standalone   Use integration
infrastructure to work with Test Director or work
as stand-alone.
23
Test Architecture -- Features
Usability Test Suite reporting facilitates easy
analysis of test execution status. Efficient
reporting mechanism helps in pinpointing test
success/failure. Reporting includes warning
messages, completion messages, pass/fail
information and assertions.
24
Test Architecture -- Features
Reliability is crystallized in the following two
aspects       Recovery from exceptions in
application       Recovery from exceptions in
Test Suite and infrastructure   Application
Recovery from exceptions would be built utilizing
the test tool features. Test Suite Generic error
and exception handling mechanism would be built
as part of the test suite infrastructure
25
Demo on ERP Product
Scenario Name Creating Purchase Indent Purpose
The Purpose of this Scenario is to define
item,creating purchase indent Authorizing
it. Test Steps 1.Login to the ltSTORESgt Module.


2 .Select Masters from the Inputs menu. In
Masters select the Item Master.

3 Enter
an Item code for the Item and enter all the
relevant details for that Item. 4.Select the
Details tab and enter the units and price for
the Item.
26
Demo on ERP Product
5. Save the record.

6. Close the
Item Master window. 7. Select Purchase
Indents from the Inputs menu.

8. Enter an Indent No. and select the Cost
Center. 9. Click the Items
tab and enter the code for the item to be
indented. 10. Click on ltADDgt to indent more
items. 11. Save the Indent.Close the Purchase
Indents window.
12. Select Authorization of
Indents from the Authorization menu. 13.
Check the Particular Prefix check box and
select the item from the list. 14. Press ENTER
against the particular item and the Purchase
Indent window gets opened. 15. Check the
details of the particular Indent in the Purchase
Indent window. 16. Save the Indent. 17. Close
the Authorization of Indents window.
27
Questions ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?