If HP and Adobe wished to prevent people from trying QTP for
automated Flex GUI testing, the current system would be an
effective mechanism. Not only do you need -- so far as anyone has
been able to determine -- to get a license to an additonal product
that you may not need for your Flex application development; you
need to install plugins, copy libraries from here to there,
recompile your application with the extra libraries, and deploy it
with a wrapper, not to mention implementing the recommended
guidelines for developing the application so as to make it work
better with the test tool. Once you have all the infrastructure in
place, and you've gotten a new trial license for your installation
of the latest version of QTP, since the original license expired
while you were trying to get everything else set up, you'll find
that playback of test scripts does not work. It turns out that QTP
9.2 does not work for Flex testing. You need to go back and get QTP
9.1. But you can't find 9.1 on the regular download site -- you
need to get a special url from HP sales. Then it turns out you
can't access the 9.1 download location, because your HP support
login and password don't work there. So it's back to sales to get a
working username and password, then download a 338 Mb zip file,
extract the contents, try to install it, and abort the installation
when says it can't proceed because you already have a version of
QTP installed. Uninstall 9.2, install 9.1, reboot for the nth time,
reapply the trial license, reinstall the plugins, and you're ready
to try the test tool. I'm pleased to report that after going
through this ordeal, and disabling tabbing in IE 7, I was able to
record and play back a minimal test. Now I just need to figure out
how to rebuild our real Flex app with the extra libraries, deploy
it, get a fresh trial license for QTP, and I'll be ready to start
serious evaluation of QTP with Flex.