Make test automation scripts domain-independent so they are reusable

Use IBM Rational Functional Tester descriptive programming so you can reuse scripts across domains

From the developerWorks archives

Shruti Grover

Date archived: December 15, 2016 | First published: March 27, 2012

In test automation, test scripts and associated test frameworks get tied to the underlying domain of the application under test. It then becomes challenging to figure out whether the same recorded objects, scripts, and reusable functions that a framework offers will work across domains. To overcome this problem, it is essential to make the automation test scripts domain-independent. The result is that the same application objects, test scripts, and reusable functions will work across different test application domains, regardless of whether they are HTML, Java, Microsoft .NET, Microsoft Windows, and so on.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

ArticleTitle=Make test automation scripts domain-independent so they are reusable