Hello Everyone,
I have seen several posts on related topics to this but none are recent and none have a solution. I am thinking that Adobe no longer really supports QTP automation in the latest version of Flex...I would love to be proven wrong but I can't find any confirmation either way anywhere online.
Here is my experience with QTP 11 + Flex 4.6 automation so far:
1.) Downloaded the trial of QTP 11 and installed it from HP - There is a missing installed cfg file which prevents the install process and the solution was to create an empty file with the same name and place it into the directory where the installer was expecting it to be. That at least got it to install. Also, I found you must uncheck the checkbox during installation that asks to run the license installer wizard.
2.) I also found you *MUST* turn off Windows 7 UAC or the application will not install properly and the add-ins will not show up. I had to go into UAC and set it to the lowest setting then restart and run the plugins .bat file to get it to work. After I did that, the add-ins showed up properly when I started WTP.
3.) I found that I had to both include all the files using the compiler arguments AND I had to include the actual SWC lib folder containing all the /automation/ SWC's from the SDK install directory or I didn't get the proper "Waiting for QTP to connect' messages when running the AIR app.
4.) Finally, I found that I had to let QTP automatically open the AIR.exe file itself on startup or QTP never connected properly. Even then, I had to try it 2-3 times before it would work and I got the QTP connected successfully message.
After all that, I can only see Flex <mx> components being logged, never spark buttons etc. This makes me feel like trying to get QTP 11 talking to the latest AIR w. Spark components may not currently be possible. Does anyone know any different?
I have seen several posts on related topics to this but none are recent and none have a solution. I am thinking that Adobe no longer really supports QTP automation in the latest version of Flex...I would love to be proven wrong but I can't find any confirmation either way anywhere online.
Here is my experience with QTP 11 + Flex 4.6 automation so far:
1.) Downloaded the trial of QTP 11 and installed it from HP - There is a missing installed cfg file which prevents the install process and the solution was to create an empty file with the same name and place it into the directory where the installer was expecting it to be. That at least got it to install. Also, I found you must uncheck the checkbox during installation that asks to run the license installer wizard.
2.) I also found you *MUST* turn off Windows 7 UAC or the application will not install properly and the add-ins will not show up. I had to go into UAC and set it to the lowest setting then restart and run the plugins .bat file to get it to work. After I did that, the add-ins showed up properly when I started WTP.
3.) I found that I had to both include all the files using the compiler arguments AND I had to include the actual SWC lib folder containing all the /automation/ SWC's from the SDK install directory or I didn't get the proper "Waiting for QTP to connect' messages when running the AIR app.
4.) Finally, I found that I had to let QTP automatically open the AIR.exe file itself on startup or QTP never connected properly. Even then, I had to try it 2-3 times before it would work and I got the QTP connected successfully message.
After all that, I can only see Flex <mx> components being logged, never spark buttons etc. This makes me feel like trying to get QTP 11 talking to the latest AIR w. Spark components may not currently be possible. Does anyone know any different?