2. Execution Approach
Framework Types
Automation Tool Used
Tool Evaluation
Application Under Test
Framework Block Diagram
Flowcharts
GUI Designing for trusted and target part
Framework Implementation
Expected and Actual Result Comparison
Report Generation
Acknowledgement
Sources
3. ExecutionApproach/Methodology :
Expectation from project:
Test data will be entered into the system under test, expected results and actual
results will be compared and a detailed test report will be generated showing all
the passed and failed cases.
Approach:
1. Test tool selection:
- List of Automation Tools which are relevant
- Selected Automation Tools will be evaluated against the features
2. Scope of automation:
- Identify all candidates (Test Cases) for Automation based on the feasibility,
business value and productivity.
3. Planning design and development:
- Automation Framework Design will be built
4. Test Execution:
- Build Platform to enable scripts addition, modification and execution.
5. 1. Linear Framework:
Script is written in step by step manner.
No functions created.
Data is hard coded.
2. Modular Framework:
All test cases are analyzed to find reusable flows.
Functions are created and then stored in external function library called test scripts.
But data is still hard coded.
3. Data Driven Framework:
Data is not hard coded in test scripts.
It is stored in some external sources like excel sheets, CSV files, databases, etc.
Test script first connects to that file and then extracts data from it.
Same script can be run multiple times with different sets of data.
4. Keyword driven Framework:
Various keywords can be created and different functions can be associated to these
keywords.
Function library is created that contains the logic to read the keywords.
5. Hybrid Framework:
Combining different features of any framework.
8. Analyzing test complete:
It is a functional automated testing platform by Smartbear.
Applications that can be tested using test complete:
1. Generic windows applications (.NET, Java or other standalone
applications)
2. Testing of web pages
• Simulate mouse actions and keystrokes on web pages
• iOS applications
3. Windows store applications
4. A runtime application that can be distributed through windows store
5. Adobe AIR apps.
9. FEATURES:
Test record and playback
Recorded tests can be modified to create new tests
Keyword testing
Scripted testing
Access to methods and properties of internal objects
Data driven testing
Name mapping feature
Test visualizer which enables quick comparison between expected and
actual screens during test
Checkpoints (a comparison operation performed during testing)
Extensions and SDK (create new plugins for special functionality)
Integration of SOAPUI, SELENIUM
JScript
VBScript
Python
DelphiScript
Scripts Support :
10. Parameters forselecting AutomationTool:
Ease of adoption
Script creation time
Scripting language
Object recognition
Learning time
Script execution speed
Framework
Whether non browser based app support
Operating system support
Device support
11. Feature TestComplete Selenium QTP
Script
Support
VBScript, Jscript, Delphi Script, Python Java, C#, Ruby, Python,
Perl
VB Script
Non-browser
support
Flex, .NET (Windows Forms), Visual
C++, Visual Basic, JavaFX
PHP , Javascript Yes
Browser
support
IE, Opera, Chrome, Firefox, (Web and
Rich Internet Application Testing)
Google Chrome , Internet
Explorer ,Firefox , Opera
Google Chrome, Internet
Explorer, Firefox
Environment
Support
Support for Win 64-bit applications Windows , Linux Only Windows
Mobile
support
Windows, Web and Mobile, Android
platform support, iOS platform
support
Android , iPhone & iPad,
Blackberry
Different commercial
product i.e.
HP UFT Mobile
Framework Calling DLL and Windows API
functions, using .NET and Java
classes,Data Driven testing, Keyword
testing
Selenium + Maven +
TestNG
Keyword, Data Driven
Continuous
Integration
AQ time integration, Integration into
Visual Studio 2013
Possible through
Jenkins/Hudson/Cruise
Control
ALM or Jenkins
Object
Recognition
Object Recognition
1) Default Object Naming
2) Name Mapping
UI Maps, XPath Element
ID, attribute DOM
Through Object Spy
Image based
Tests
Need workaround XPath Element ID Easily possible
Software Cost Licensed Zero Licensed
Coding
Experience
Should be very good Good enough Not Much
Script Creation
Time
Less High Less
Memory
consumption
Less Low High
Product
Support
Smartbear Support Open Source Community HP support
Tool
Selection:
12. Automation Tool Evaluation Score
S.No Tool Features Test Complete Selenium QTP/UFT
1 Technology Support 3 0 2
2 Ease of Script Development 2 1 2
3 Language Support 3 2 1
4 Mobile Support 3 2 1
5 Framework 3 1 2
6 Continuous Integration 3 2 2
7 Customized Reporting 3 2 2
8 Test Independence 3 2 2
9 Script Maintenance 2 1 2
10 Memory consumption during execution 2 2 1
11 Non browser support 2 0 2
12 Multi Browser Support 3 2 2
13 Data Driven Capability 3 2 2
14 Object Recognition/Storage 3 1 2
15 Ease of Object Store Maintenance 2 0 2
16 Image based tests 2 2 3
17 Coding experience 2 1 1
18 Learning Resources Availability 3 1 2
19 Product Support 3 0 2
20 License Cost 1 3 1
Total Score 51 27 36
Score Description:
0 - Doesn’t Meet Requirement
1 - Meets Requirement Partially
2 - Meets Requirement
3 - Exceeds Requirement
Tool Evaluation:
16. IDM Use Cases to be Demonstrated:
• Trusted Side:
• Create User
• Update User
• Enable User
• Disable User
• Target Side:
• Account Creation
• Account Provisioning
43. Sunil kumar sao,
Director, Delivery
- for his non-stop support for the project.
Bharat Katkar,
Senior Manager, Delivery
- for guiding me throughout the project.
Supriya Raut,
Senior Software Engineer, Delivery
- for giving me a walkthrough on Identity Creation portion.
Vijay Naik,
Manager-Qa, Delivery
- for his guidance on the Account Verification Part.
Rahul Patil,
Technical Lead, Delivery
- for describing the Access Policies Part.
