Inflectra and Alexey Grinevich presented a live webinar on Playing UFT/QTP Scripts with Inflectra’s Test Automation tool - Rapise. This event originally took place on November 30, 2021, at 10 am (EDT). WHY THIS WEBINAR? Rapise contains a Converter tool enabling execution of UFT scripts in Rapise. Your QTP/UFT test scenario and even frameworks, with external steps, shared and local repositories, custom functions and libraries may be converted and executed by Rapise. The goal of this webinar is to shed more light on this feature. WEBINAR AGENDA: During the webinar, the speaker will explore the following topics: - Rapise v7.1 in the nutshell - How to convert QTP/UFT test scenarios, frameworks, repositories, libraries using Rapise - How to execute QTP/UFT test scenarios using Rapise. WEBINAR PRESENTER: Alexey Grinevich is a Software Developer at Inflectra Corporation. He is one of the creators of the Rapise test automation tool. He holds a master’s degree in computer science and a Ph.D. in Applied Mathematics and has been working in the IT industry for the past 20 years in areas such as compilers, computer languages, runtime debuggers. For the last ten years, the major interest is software for automated testing. At Inflectra, Alexey has been responsible for researching the tools, technologies, and processes in the software testing and quality assurance space for the past five years. His special interest is legacy APIs and desktop system testing. Check out the webinar recording on our YouTube Channel!>> https://www.youtube.com/channel/UCAfIwdACxf_X9qb60fsuSiA

1. ®
WEBINAR: Playing UFT/QTP Scripts
with Rapise
• November 30th, 2021 – Alexey Grinevich,
alexey@inflectra.com
We will be starting the webinar shortly, please stand
by…
All phones will be automatically on mute until the
Q&A.

2. ®
Hey, I am Alexey
• Working on Rapise test
automation tool @Inflectra
• Over 20 years in software
development
• 12 years in test automation
• Email: alexey@Inflectra.com

3. ®
3
Plan
 Conversion options
 Prerequisites for conversion
 Conversion steps
 Conversion overview
 Estimates

4. ®
4
®
Conversion Options
 Convert from UFT style to Rapise Style

5. ®
5
®
Conversion Options
 Create test from Scratch (re-record)

6. ®
6
®
Conversion Options
 Emulate UFT in Rapise, keeping UFT-style

7. ®
7
®
Conversion Options
 Create test from Scratch (re-record)
 Convert from UFT style to Rapise Style
 Emulate UFT in Rapise, keeping UFT-style

8. ®
8
Prerequisites
 UFT
 Rapise
 Converter
 Excel

9. ®
9
Steps
1
Step 1: Prepare
UFT Tests
2
Step 2: Prepare
Converter
3
Step 3: Convert
4
Step 4: Run &
Post-process

10. ®
10
Step 1: Prepare UFT Tests
 Should be exported from ALM
 External Steps
 Data Files
 Should PASS before conversion
 Should be set within folder structure:
 Test Solution
 Test Case 1
 Test Case 2
 Test Case 3
 …

11. ®
11
Step 2: Prepare Converter
 (Inflectra)
 Analyze tests
 Find matching lib
 Prepare automatic converter project
 Implement missing entry points (if any)

12. ®
12
Step 3: Convert
 Libraries
 Shared Repositories (Objects, Checkpoints)
 Test Cases
 Scripts
 Local Repositories (Objects, Checkpoints)
 XLS Data Tables

13. ®
13
Step 4: Run & Post-process
 Execute test
 Sometimes fix VBS (.mts) to remove ambiguities
 Fix other things:
 Encrypted passwords
 Dictionaries
 Errors forgiven or ignored by VBS
 Spreadsheets (Corrupted excel files)

14. ®
14
®

15. ®
15
®

16. ®
16
®

17. ®
17
®

18. ®
18
Summary
 Converter makes script keeping UFT script structure
 Converter needs tuning
 Once tuned it is automatic
 Minor tweaks may be needed to source tests

19. ®
19
Q&A
Thank You!

20. ®
20
Excel Files Fix
 Some excel files (Default.xlsx) are corrupted
 MS Excel may fix them
 If Excel is installed on the converter hosts, it gets converted
automatically

21. ®
21
Overall Flow
Prepare Converter 5-30%
Convert Tests 1%
Prepare UFT Tests 5-20%
Run & Post Process 50-70%

22. ®
22
Test Conversion Estimates
 Test should be executed 10-20 times during conversion

23. ®
23
Potential Problems
 Long tests
 Rare tests (once per day, once per week etc)
 Case Sensitivity
 Undeclared Variables
 JS keywords as var/function names
 Data locked in ALM
 Internal API Usage