Modularity-driven testing: Difference between revisions

Revision as of 13:41, 29 May 2012

Latest revision as of 05:21, 8 July 2023

(19 intermediate revisions by 14 users not shown)

Line 1:

'''Modularity-driven testing''' is a term used in the testing of [[software]]. The test [[Script (computer programming)|script]] modularity [[Software framework|framework]] 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.<ref>{{Cite book |last1=DESAI |first1=SANDEEP |url=https://books.google.com/books?id=B4sQDAAAQBAJ&dq=Modularity-driven+testing+framework&pg=PA157 |title=SOFTWARE TESTING : A Practical Approach |last2=SRIVASTAVA |first2=ABHISHEK |date=2016-01-30 |publisher=PHI Learning Pvt. Ltd. |isbn=978-81-203-5226-1 |language=ar}}</ref>

<!-- Please do not remove or change this AfD message until the issue is settled -->

{{Article for deletion/dated|page=Modularity-driven testing|timestamp=20120529134144|year=2012|month=May|day=29|substed=yes|help=off}}

<!-- For administrator use only: {{Old AfD multi|page=Modularity-driven testing|date=29 May 2012|result='''keep'''}} -->

<!-- End of AfD message, feel free to edit beyond this point -->

{{Unreferenced|date=March 2007}}

{{Portal|Software Testing}}

==Background==

'''Modularity-driven testing''' is a term used in the testing of [[software]].

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]] 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|website=[[IBM]] |url=http://www.ibm.com/developerworks/rational/library/591.html|accessdate=2013-02-22}}</ref>

==References==

==Test Script Modularity Framework==

The test script modularity framework 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.

{{Reflist}}

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.

{{DEFAULTSORT:Modularity-Driven Testing}}

[[Category:Software testing]]

{{comp-sci-stub}}