How does your Structural Testing for web apps compare with QTP's "Descriptive Programming?" Sounds like the same thing, eh?

Actually, when you try out our Structural Testing commands you will probably find that they are a lot simpler.

For one thing, these commands are engineered so as to NOT require programming skill. You have a basic command to help you identify some spot on the page -- IndexFindElement or IndexFindElementEx.

Then you have basic commands to move up or down from there to the element that you want to act on.

Finally, you have simple commands to act on the element (with the assumption that the action you take is one that the particular element will respond to).

The eValid PageMap provides some detail about every element in the page, but you don't have to be a programmer to use that, either.

All in all, then, eValid's approach is to support non-programmers -- but programmers will find the simplicity of the approach trivial to learn and a joy to work with.

eValid Support