Thanks for the detailed reply. Considering that TestComplete can be run to record, with a small widget in the corner, it wouldn't be a stretch to ask for a mode of running a script step by step, until we hit a problem, so we can see what it's doing.
I get the questions, but I'm not sure what I'm supposed to be doing differently. I record as I perform tests, then edit them as needed if they can't be played back properly. I'm told that cross browser testing should be as simple as choosing another browser to point to, and go.
I mean, that's basically what it says on the tin, right?
What am I supposed to be doing to carefully identify objects? What is the object spy?
I did take a peek in name mapping editor, but don't notice anything special.
Sorry for the noob questions, but this was supposed to be simple to use and work with. I expect some editing to be needed, of course.
I mean, this is what's on the site:
"
After you create tests, you can run them with minimal or no changes in all the supported web browsers. Cross-browser support includes not only the test object names and hierarchy, but also a unified approach for working with browser messages and dialogs and objects' data. With browser independent tests, it is easy to create test suites that repeat the same test under different browsers registered on the test machine. To test different combinations of web site versions, browsers and operating system versions you can take advantage of the support for distributed testing and additional TestExecute licenses. "
Not seeming to be the case.
Thanks,
Peter
