Structural Testing: Making Web Tests More Durable

We often hear users complaining that their web pages changed and the tests that used to PASS yesterday now FAIL. Is there anything that can be done to have tests endure page changes that don't affect functionality, they ask?

The answer lies in the use of the Structural/Algorithmic Testing testing approach. Instead of basing test on properties of the page, when a particular feature is likely to move around, the test is based on (pivots on) that feature. The result (as the table outlines) is a little bit more work in exchange for a much higher level of durability -- without any loss in test quality (no increase in false-negative results).

A simple technique that we recommend, a Manual Script Creation Process, takes the mystery out of converting a "from life" recording into a highly durable validation test. Once the key page elements are identified, you modify the script using the Structural Testing Commands.

P.S. If this structural testing approach still isn't strong enough for your needs, with some additional programming effort you can exploit the eValid Programmatic Interface [EPI] to create a C++ program that runs your test at any level of durability you want.