SFS Test Automation

Test Automation
Presentation by
ABDUL KALAM
Synergy Financial Systems Limited 1
Who Are We:
Financial Software Provider Company
• Headquartered in United kingdom.

Location throughput …
• Experts professionals
• Rapidly growing and profitable
Synergy Financial Systems Limited

2
Agenda
• Software Testing Challenges – Automation Context

• Test Automation Perspective
• Value Proposition
• Synergy Test Automation Process (STAP)
• Test Automation Architecture
• Test Automation – Demo
• Synergy Expertise

Software Testing Challenges: Regression Testing
•Third Party Products

•Deployment Config
Test Object
•Database
•Operating System
•Browser
 Bug Fixes
 Minor Modifications
 New Functionality
 Integrations
Test Environment
 Service Packs
 Patches
 Interfaces
Software Testing Challenges : Coping with development
Development time
Version 1.0 Version 2.0 Version 3.0

5000 days 2500 days 2000 days
Test time
Version 1.0 Version 2.0 + 1.0 *Version 3.0 + (2.0 + 1.0) *

5000 days 2500 + 2500 days2000+ 1250 + 2000 days
* Impact Analysis testing

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.

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 ‘Quality’:Health of the product
 Insight about the risks Quickly
 Consistency across test runs
 Test frequently and thoroughly
Should I go for 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

Synergy Test Automation Process (STAP)
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.

STAP
Feasibility Study
Proof of Concept
Identify the Scenarios
Design/Record the Script
Modify the Test Script
Run the Test Script
Test Suite
Maintenance
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

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 re-usable scripts with application and data

integrity.
POC will help the client to understanding automation efforts and

experience the time saving and capabilities of Synergy Test
Automation skills.

STAP….
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. 13
STAP…
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.

Test Architecture
Data
tables
Business Business
Function 1
Function Generic
Business
Driver Function 1
Function 2 N Script
Generic
Function 2
Cleanup
Generic
Scripts Function N
Log Object Repository

Files
Reports
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.

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.

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.

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.

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.

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

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.

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.

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

Demo on MM Product
Scenario Name: Creating Message

Purpose: The Purpose of this Scenario is to define item,creating
message & Authorizing it.
Test Steps:
1.Login to the <User> Module.
2 .Select “MM” from the Application
menu. In “MM” select the “Enter”.
3 Enter an input for the message
and enter all the relevant details for that message.
4.Select the “Enter” tab and enter for validation.

Demo on MM Product
5. Save the message.
6. Close the “MM” window.

7. Select “Verify” from the “MM” menu.
8. Enter prompted value and select the verify tab.
9. Click the “verify” tab and enter the “Password”.
10. Click on <OK> to verify.
11 . Close the “verify” window.
12. Select “Approve” from the “MM” menu.
13. Search the “Message Type” and select the item from the list.
14. Press ENTER against the message and the “Approve” window gets
opened.
15. Check the details of the message window.
26
Questions ?
?
?
?
?
? ? ? ? ? ? ? ?
?
?

Thank
You...

SFS Test Automation

Uploaded by

Copyright:

Available Formats

SFS Test Automation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SFS Test Automation

Uploaded by

Copyright:

Available Formats

Test Automation

• Headquartered in United kingdom.

Synergy Financial Systems Limited

• Software Testing Challenges – Automation Context

Synergy Financial Systems Limited 3

•Third Party Products

Version 1.0 Version 2.0 Version 3.0

Version 1.0 Version 2.0 + 1.0 *Version 3.0 + (2.0 + 1.0) *

* Impact Analysis testing

Synergy Financial Systems Limited 6

 Reduction in testing costs

 Test effort levels

Synergy Financial Systems Limited 8

Synergy Financial Systems Limited 9

Design/Record the Script

Modify the Test Script

Run the Test Script

Organization Related Feasibility:

Synergy Financial Systems Limited 11

POC helps in understanding the reality of Automation.

Result of Automation is re-usable scripts with application and data

POC will help the client to understanding automation efforts and

Synergy Financial Systems Limited 12

Design & Record the scripts: Design Hierarchical directory

Modify the test scripts: Test scripts will be modified with

Test Suite Maintenance(TSM): TSM is fully dependent of Test

Test Architecture is friendly for incorporating the new functionality,

Synergy Financial Systems Limited 14

Log Object Repository

Driver Script : Each test script is independent of the other scripts.

Synergy Financial Systems Limited 16

Start up Script: Initializes the test environment related parameters.

Object repository: All the GUI objects in the application would be

Synergy Financial Systems Limited 17

Synergy Financial Systems Limited 18

Maintainability: Test Automation Suites generally undergo changes in

To minimize the re-work effort, each area of impact is effectively

Synergy Financial Systems Limited 19

What is unique in this Architecture?

In this architecture we have followed Object Oriented design, All the

Synergy Financial Systems Limited 20

Synergy Financial Systems Limited 21

Portability: Test Suite portability is built around three aspects:

Synergy Financial Systems Limited 22

Usability: Test Suite reporting facilitates easy analysis of test

Synergy Financial Systems Limited 23

Reliability is crystallized in the following two aspects:

Application: Recovery from exceptions would be built utilizing the

Synergy Financial Systems Limited 24

Scenario Name: Creating Message

Synergy Financial Systems Limited 25

6. Close the “MM” window.

Synergy Financial Systems Limited 27

Synergy Financial Systems Limited 28

You might also like

Version 1.0 Version 2.0 + 1.0 Version 3.0 + (2.0 + 1.0)