 Issues designing and running tasks
We just purchased a license of AA Enterprise 4.5 in a large government organization.
We do massive testing of Commercial Off The Shelf (COTS) applications.
For example, we test Word 2003, Project 2003, visio 2003, Adobe Acrobat 8 to name a few on a variety of baseline platforms.
I am currently designing a testing methodology based on AA 4.5 and I'm having some conceptual issues. I personnally recommended it based on the trial version but I'm starting to panic because, although our testing seems to be a "text book" case for AA, I'm starting to doubt it will do the job.
Basically, I want to deliver a solution that is "modularized" and relatively easy to maintain.
Issues/questions:
1) I need to use a multitude of tasks, basically, one for each tested apps. But I realized that if you launch an .exe, it will be slow overall because the runtime is loaded everytime, say 20 times. Is there a way to load a first exe and then call up addidional separate tasks that are not compiled (.atmn)? (we cannot install AA on each tested computer)
2) As a workaround for my issue described above, I set to copy paste all my separate tasks into one main one. Well, is it possible that AA gets confused with the windows names? For exemple, there a lot of "Save as" windows and sometimes AA stops because it can't seem to find the right one. So is is a bad idea to "cut and paste" task code?
3) Also, I recall (in the trial version) having seen "screenshots" of the various windows used in a recorded task. I cant seem to find those anymore...
4) Is there a way to list or view everything that is being done by AA in the background? I noticed AA mimics keyboard input to the letter, including delays etc where are those delays? They're not in the source code.
5) Often, some windows are being shifted (re-positioned) slightly during a task execution - why is that? I can't figure this one out.
6) Is there a way to "branch" in the task code? Like goto's? Sometimes it's convenient to bypass sections of code. I haven't found the debugger usefull in that regard.
Thanks for your help  |