Modularity-driven testing: Difference between revisions

Revision as of 20:56, 22 February 2013

Revision as of 00:01, 7 March 2013

Line 7:

Of all the frameworks, this one should be the simplest to grasp and master. It is a well-known programming strategy to build an abstraction layer in front of a component to hide the component from the rest of the application. This insulates the application from modifications in the component and provides modularity in the application design. The test script modularity framework applies this principle of abstraction or encapsulation in order to improve the maintainability and scalability of automated test suites.

<ref>{{cite web|last=Kelly|first=Michael|title=Choosing a test automation framework|url=http://www.ibm.com/developerworks/rational/library/591.html|accessdate=2013-02/-22/2013}}</ref>

==References==

<references />

{{DEFAULTSORT:Modularity-Driven Testing}}

[[Category:Software testing]]

==References==

<references />