Escolar Documentos
Profissional Documentos
Cultura Documentos
Presenter : Nadeem S A
Designation : Test Manager
Email : nadeem@relq.com
Introduction
Constraints in Manual Testing approach
What is Test automation?
Implementing Test automation for Higher productivity
Feasibility Analysis
Tools and their selection criteria
Test script development methodologies
Test Automation frameworks
Case study
Conclusion
Q&A
2
Introduction
3
Software Testing
4
Software Testing
Is a specialized task
5
Challenges In Testing
6
Challenges
7
Productivity Constraints of Manual Test Approach
8
Manual Test Approach - Constraints
9
Manual Test Approach - Constraints
10
Why consider Test Automation?
11
Test Automation
12
What is Test Automation?
13
Implementing Automation for Higher Test Productivity
14
Test Automation Process
Enhancement of
test scripts
Test summary report
15
Importance of Feasibility Analysis
16
Feasibility Analysis
17
Feasibility Study
18
Selecting the Automation Tool
19
Selection criteria for Automation tools
TYPE OF TEST
Functional Testing
Silk test, Winrunner, QTP, Rational Robot, Test Complete,
Test partner
Performance Testing
Load Runner, Silk Performer, QA Load
Unit Test
JUnit, NUnit
Test Management
Test Director, Silk Central, Quality Center, QADirector
USABILITY
Ease of use of tool features
20
Selection criteria for Automation tools
COMPATIBILITY
With the application for current and future needs
With required OS (Windows XP / NT / 2000 / Unix / Linux)
With required Browsers (IE, Netscape etc)
LEARNABILITY
Adequate Training material and technical support
Online Community
CAPABILITY
Support for Java / .NET / Oracle Tech.
Support for Client Server / Legacy Systems
21
Automation – Specialization in Testing
22
Setup best practices
Capture the requirements by involving end users of the
suite
23
Set up Best Practices
24
Plan for maintenance and use
25
Test script development
26
Test script development Methods
Record and playback
Data driven
Keyword driven
Hybrid
27
Record and Playback approach
28
Record and Playback approach
Advantages:
Less effort for automation and quick Returns
Does not require expertise on the tool
Limitations:
• High dependency on the GUI of AUT
Scripts contain hard coded data
Not a recommended approach for developing scripts.
29
Data Driven approach
30
Data Driven suite - Architecture
Additional Info:
APPLICATION UNDER TEST
31
Data Driven approach
Advantages:
Data is separated from scripts and stored in data files
The volume of test data and its combination can be increased for
exhaustive testing
Limitations
Application must be available to start scripting
32
Keyword driven approach
33
Keyword driven approach – Sample Action file
34
Keyword driven suite Architecture
Additional Info:
35
Keyword driven approach
Advantages:
• The User can easily create the test scenarios by grouping a set of
Keywords in the Action files.
• The action files can also be a single point of reference for Manual
and Automated Test cases.
• Maintenance is easy as changes in functionality require changes in
Action Files only
Limitations:
• The number of action files increases with functionality.
• The initial effort to design is more compared to data driven approach
• Users will have to be trained on the use of Keywords
36
Hybrid
Advantages:
Limitations:
Maintenance is an issue.
37
Test Automation Framework
38
What is a Framework?
39
Objectives of Automation Framework
40
Objectives of Frameworks
41
TYPES OF AUTOMATION FRAMEWORKS
42
Types of Frameworks
Process framework
Test Framework
Hybrid framework
43
Process Framework
44
Process Framework - Advantages
45
Test Framework
Functional Test1
Project A
Functional Test2 Repository
Of
−Test cases
−Test Scripts
Functional Test1
Project N
Functional Test2
46
Test Framework - Advantages
Re-usability of components across projects reduces
redundancy
47
Hybrid Framework
48
CASE STUDY
49
Case Study 1
50
Case Study 1
Develop test automation suites using Silk test for the following.
51
Case Study 1
Test requirements
No of Products = 2
No of Test cases = 1400 test cases each for US and
Localized builds (BEFIGS Languages) = 1400 x 7
Average No of builds per product for US = 10, BEFIGS = 10
Challenge
Manual Execution of all test cases on all environment –
Impossible.
Solution
Framework based Automation
52
Case Study 1
53
Case Study 1
SL COMMAND DETAILS
NO PARAMETERS
1 Go Command to initiate the execution of the test
54
Case Study 1
55
Case Study 1
Perl scripts
OS images
VM Ware
56
Case study 1
57
Case Study 1 - Architecture
Test Repository
1.Test Scripts
2.User Defined
Library
Test Script Test Environment
Test Script
3.GUI files Selection File/
Selection File/
4.Utility Scripts SCM
SCM Test Client
5.Test data files Test Client
Machine cluster
6.Tool Installer Machine cluster
.…
.… Test
database
TestController
Test Controller (optional)
Test Controller Script
58
Case Study 1
Te st Effort re duction
15
Effort in days
10
0
Manual Automated
Type of Testing
59
Case Study 1
100
80
build
60
40
20
0
Manual Automated
Type of Te s ting
60
Case Study 1
150
Effort in minutes
100
Ef f ort
50
0
Manual Automated
Type of Te s ting
61
Case Study 2
The Client
– A leading Bank having operations across the globe
The System
– Online Cash Management System, with support for
multiple branches
Methodology
– Keyword-Driven
Scripting languages
– Perl, VB Script
63
Case Study 2
64
Case study 2
65
Case Study 2 - Architecture
66
Case Study 2
140
120
100
80
Effort
60
40
20
0
Manual Automation
Type of Testing
67
Case Study 2
Improvement in Test Cases execution coverage
Task Initial Coverage Current Coverage Improvement in
coverage
Executing test cases 50 % 90 % 40 %
Improvement in Coverage
100
80
%Coverage
60 Manual
40 Automation
20
0
Coverage
Type of Testing
68
CONCLUSION
69
Conclusion
70
Conclusion
71
Q&A
Thank You
73