Modularity-driven testing: Difference between revisions

Revision as of 02:22, 21 March 2018

Revision as of 22:52, 27 March 2018

Line 5:

==Test Script Modularity Framework==

The test [[Script (computer programming)|script]] modularity [[Software framework|framework]]{{dn|date=March 2018}} requires the creation of small, independent scripts that represent modules, sections, and functions of the application-under-test. These small scripts are then used in a hierarchical fashion to construct larger tests, realizing a particular test case.

Of all the frameworks, this one should be the simplest to grasp and master. It is a well-known [[Computer programming|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 (computer programming)|encapsulation]]{{dn|date=March 2018}} 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}}</ref>

==References==