question #2 from a pre-newbee:
In the "Getting Started" manual I read you have to define the AUT explicitely to a TC project. Now, our "AUT" consists of multiple instances of the same executable each using a different startup configuration. And then, this exe spawns new processes as well, which might not really known to the tester.
How would you manage to declare the AUT to TC in this case? Sounds difficult to me.
Re: Define AUTs
TC automatically recognizes any objects that you work with based on the process, window and other parameters related to it.
If you are using the record and playback mechanism, I would suggest putting a breakpoint and observing the 'object browser' to learn more about how different processes and windows are recognized.
This will help you understand what is going on.
Yeah, you need to define the main executable from where you want to start if TC is going to invoke the .exe in the first step.
However there are various ways of overcoming it, usually by executing the exe in other ways. For e.g. open the windows start menu, run, and in the cmd window type something....