Not too familiar with automated testing, but I have an application where the (manual) test scripts we have now require checking on other systems at certain points. How would this translate into an automated tool like qtp/winrunner? Is it possible to have scripts in these tools which would execute to a certain point, and then wait for a user to manually check something before clicking a button to continue the script?
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!
[ QUOTE ]
Why would you know have QTP or WinRunner open the other application capture the result, do a verfication and then continue in the original app??
[/ QUOTE ]
well for example, we might have a process where at some point the user has to physically scan something (an invoice for instance) into the system. Or there may be a portion of the process that is so dynamic and data-driven that its not feasible to script. I wasnt sure how that type of situation is typically handled in the automated testing world.
I've had a few situations in the past where I have wanted to include manual steps within an automated test.
The user dialogs are a good way to go here.
One thing to consider, is that often you want these tests to run in an unattended fashion. But, since a dialog box is inherently "attended", you may wish to make this part of the script conditional, based on some argument passed to it, or some configuration file.
That way, you can run the same script in "attended" or "unattended" mode.
In unattended mode, the dialog might not appear (or might dismiss itself after a certain period of time), and will not interfere with the remainder of the script.