Easily & Painlessly Migrate from QTP/UFT to TestComplete
•Download as PPTX, PDF•
0 likes•701 views
Changing testing tools can be daunting, but it doesn't have to be! Learn how to painlessly migrate from QTP/UFT to TestComplete with members of our team.
Recommended
Recommended
More Related Content
Similar to Easily & Painlessly Migrate from QTP/UFT to TestComplete
Similar to Easily & Painlessly Migrate from QTP/UFT to TestComplete (20)
More from SmartBear
More from SmartBear (20)
Recently uploaded
Recently uploaded (20)
Easily & Painlessly Migrate from QTP/UFT to TestComplete
- 1. Easily & Painlessly Migrate from QTP/UFT to TestComplete
- 3. Page What’s Going On? 3 + Highly Profitable, Mature Products Fast-Growing Market Tools
- 4. Page What Does this Mean? 4 • Cash vs. Equity • Betting on large future returns • Pressure from Investors • Equity is 70% of value • Value is 3X current revenue • Execution Risk • Micro Focus has grown 3X their size • Borrowed capital
- 5. Why Migrate?
- 6. Page How Does This Impact Current Customers? 6 Will there be any change to the products or services you are receiving? Will there be any change to the prices you are paying?
- 8. Page How Does the Tool Work? 8 Migrator tool allows users to effortlessly convert the UFT/QTP Scripts to TestComplete VB Script with just a few clicks. It converts UFT/QTP project files/components to Testcomplete 12.xx versions and above. High level steps as described below: Select UFT Project/Solution to Migrate 1. Select Destination Folder 2. Start Migration Some key indicators of the migrator as below: Major UFT/QTP features migrated Migrator loads all files within the project and processes to transform to Testcomplete VB Script Project Migrates Shared/Local Object Repositories to Name Mapping Migrates the Actions/Functions/Subroutines in UFT to Testcomplete Script Units (.svb) files Migrates any Global/Action Data tables used in UFT to use DDT methods in Testcomplete Supports custom folders / file structures Migration log to analyse migration and debug Partial migration details are captured in log and script files
- 9. Page Prerequisites for QTP/UFT Migration 9 Source UFT/QTP Automation Project Access to stable application and other components related to Source UFT/QTP Automation Project Current execution result of source UFT/QTP Project List of known script issues in source UFT/QTP Project
- 10. Page Migration Options 10 Most suitable for UFT/QTP project developed using UFT/QTP standard features Low complexity frameworks UFT-TC migration feasibility check Less than 50 Test Scripts FREE MIGRATION Most suitable for Framework based projects Greater custom code used Descriptive Programming used Usage of any 3rd party tool, Database etc. Larger volume of Test Scripts Transition of entire QTP/UFT script repository NOUS-LED PAID MIGRATION QTP/UFT – TC MIGRATION OPTIONS
- 11. Page Package Options 11 Features Free Migration Nous-led Paid Migration Object Repositories upto 3 >3 Actions upto 50 >50 Data tables (Action based) upto 50 >50 Functional Libraries upto 3 >3 Environment Variables upto 3 >3 Recovery Scenarios upto 3 >3 Checkpoints upto 3 Complete support Descriptive Programming Less support Complete support Framework support Less support Complete support Customized Code Less support Complete support QTP old versions Less support Complete support Suggestions / Improvement for existing automation No Yes
- 12. Page 12 Free Migration Process
- 13. Page 13 Nous - Led Paid Migration Process
- 14. Page Some Final Thoughts 14 • Change is let us help you! • Innovative products with new features • Fast & expert support every step of the way
- 15. Thank You!
Editor's Notes
- For the past year you’ve probably heard some news about a merger that has happened between HP and MicroFocus. HP has decided to focus on its infrastructure rather than its application software. And because of this they spun off their software division and MicroFocus ended up buying it. HPE recently sold its software assets to Micro Focus in an $8.8 billion transaction—making Micro Focus one of the world’s largest pure-play software companies. So you may be asking yourself—what products went over to MicroFocus? Well there are two types of products that came from HP The first are highly profitable, mature products. These include tools that HP acquired through the Mercury transaction such as ALM, QC, LoadRunner The second is fast-growing market tools These include tools like enterprise security and data analytics Some examples of the products you may have or at the very least have heard of include: UFT, LoadRunner, and ALM
- But ya know there’s a lot more than just Micro Focus acquiring HP’s old products so you may be asking yourself what does this mean? As we mentioned of this 8.8 billion dollar number, 2.5 billion was in cash while 6.3 billion was equity…. Meaning 70% of this deal is banking on future value of the company or in other terms is “speculative.” Micro Focus ended up paying 3x the current revenue of HP all while the industry has been witnessing a decline in the HP revenue. With this much of the deal banking on the success of the future there are two things to consider….. Pressure from investors and execution risk. These two things go hand-in-hand but there are many factors to consider. The first risk is purely from an execution side of things. Micro Focus has grown 3 times their size. While they have demonstrated continued success with acquisitions in the past… this one is a little different due to just the size of this acquisition. They also had to borrow a lot of capital so there will be much pressure from investors to make up this value in the future in order to pay off the debt in the next couple of years. So now you have to wonder.. How will Micro Focus mitigate these risks? There are two main ways that this will happen: increasing their margins and increasing their revenue Which leads us to okay we know what’s happening, what it means, but now… why should you care?
- So, why should you care? Well you should care because at the end of the day you care about two things… how much you’re paying for something and what you are getting for it. This is only further exacerbated by the issues that Micro Focus currently has the same organization when looking at their products that HP does. They are separated into highly profitable mature products and faster growing market tools. When looking at the product consolidation that Micro Focus will undergo it makes sense that there will be more investment in the current faster growing products and cost reduction of the mature older products This could lead to higher license cost or decrease in support and innovation. I don’t know about you but if I was paying for a product I would want to bank on the company to continuously focus on improving the product while also having a fast and expert support team to help me if I ever ran into any problems. Also… you should think about… what happens to the overlapping assets between HP and Micro Focus? In many ways this is a horizontal merger in the same industry where the same products meet the same needs. An example would be UFT & Silk Test… will both continue to be around ? If so, how do you consolidate costs? Which will stay relevant?
- High level diagram of how the tool works