Modularity driven testing
What does the term 'modularity' imply?
Modularity refers to a single component or a module. A collection of modules completes a software application. Therefore, when we talk about modularity driven testing, it implies testing a specific module. It requires creating test scripts individually for each of the modules, execute them and validate its execution results. Gradually as the testing progresses, the individual modules are combined together to form a larger unit.
Types of Modular driven framework :
- Test script modularity framework - As the name suggests, test script modularity framework is meant for creating scripts that may represent either a module or a function for the application under test. Henceforth, these modules are integrated with the purpose of finalising the complete application.
- Test Library architecture framework - Test library architecture framework is based on a similar concept as mentioned above, the only difference lies in the fact that it segregates the application under test into different functions and procedures. This may involve creation of library files namely - SQAbasic libraries, API's, DLL's etc.. These library files are invoked by the test scripts.
- Automation time is definitely reduced to a great extent as division of modules shortens the time span.
- Performance is higher.
- While building any single component, it is possible to execute and debug the code at the same time.
- There is one prominent drawback in modular testing, it is less efficient than other frameworks like keyword and data driven.