| || |
C++ MFC to C#.Net Conversion effects on QTP Test
I am currently working to develop an Automation Test Framework using QTP. In this framework I plan on using a shared repository. Currently, the GUI apps that I need to test are C#.Net and C++ MFC with many custom ActiveX controls.
The plans are to convert the C++ MFC GUI apps to C#.Net mid-next year.
While I am just starting to implement this ATF, what can I do now to reduce the amount of re-work after this conversion.
Re: C++ MFC to C#.Net Conversion effects on QTP Test
I am in the process of building some an QTP automation Framework also, any suggestions on this topic?
I have used WinRunner primarily for the past years and we have a framework with it, which we used shared checklist, guimap and function libraries. So far, my understanding with QTP is that I can use a shared OR, a .vbs as function library. How do I make a shared check list?