![]() |
| |||||||
Testing Anywhere Post messages and questions related to Testing Anywhere here. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
|
I have created a recorded test. If I use the Run Button to launch the test the test fails , But if I go into the edit mode and click the 1st command and run from here it passes fine.. What is the diff between the run button and run from here..TIA Ron |
| |||
|
I’m running into many of the same issues. First I want to say, I have been using TA for 3 weeks to automate a test as a proof of concept, to see if TA will do what I need. If not I’ll purchase QTP-11 and be done with this nonsense. I think the concept of TA is sound and I can develop tests very quickly, maybe 5-10x than QTP. The problem is I have lost all of that time due to constant failures in the test due to window operations that TA fails to handle properly. I think besides buggy TA code, the documentation is horrible. None of the commands are fully documented with in depth info, so people assume that TA will properly handle window timing issues, focus being stolen etc etc. The documentation that is available, are a few screen shots and a couple of step by step examples, that are very simple and not nearly informative enough. I get what TA was trying to do, make it simple for non programmers, but they blew it in the documentation. Non programmers need tons of documentation and examples on how to do it right and how to get around TA limitations. To add extreme insult to injury… there are no code examples on their web site, so people could see how the TA experts recommend using their features. Cut and paste code into their own code etc (maybe they cant get their code to work reliably either ?) Below is an example of 4 lines of code that were driving me crazy It would intermittently fail, but running from this step always worked; Close Excel Begin Error handler If pop up, select yes End error handler To get reliable operation (for now) I had to add my own delays, activate windows that should be active already etc, I expect these will fail if my test pc get bogged down etc. Close Excel Delay 1000ms Begin Error handler Activate pop up Delay 200ms If pop up, select yes End error handler |
![]() |
| Thread Tools | |
| Display Modes | |
| |