Modularity-driven testing

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

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.

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.[1]

gollark: The wiki says```A flag, mod_IC2.suddenlyHoes (added in 1.337), can change the probability weight of Wooden Hoes to 9001, reducing the chances of getting anything other than Wooden Hoes to 0.53% (about 1 in 186).```so I think it's some sort of overrunning april fools'...
gollark: I think the weights got messed up.
gollark: It dispenses scrapboxes, which is meant to produce random items, but I only get... wooden hoes.
gollark: The Wooden Hoe Generator!
gollark: In extreme hills.

References
  1. Kelly, Michael. "Choosing a test automation framework". Retrieved 2013-02-22.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.