This section explains how to make test suites reusable. For a step-by-step demonstration of how to construct and use a reusable test suite, see Creating Reusable (Modular) Test Suites.
| Table of Contents |
|---|
Introduction to Reuse/Modularization
In many cases, you may want to create a test suite that can be reused by other test suites. A common example is a test suite that logs in to a web site. Once such a test suite is created, it can be used by other test suites in various scenarios that require a login.
...
- Referenced test suites: Once a reusable module or test suite has been created, it can be referenced by another test suite.
- Variables: You can parameterize tests with variables, which can be set to specific values from a central location, set from data sources, or set from a Data Exchange or Extensions tool.
Using Test Suite References
| Anchor | ||||
|---|---|---|---|---|
|
Adding an existing test suite as a test suite reference is especially useful if you have a test suite that you would like your team members to reuse across multiple parent test suites.
...
If a referenced test suite is modified, for example, it is moved from its original location in the Test Case Explorer, changes will be propagated to the parent by closing and opening the test or restarting SOAtest.
Using Variables
For details on using variables, see Defining Variables.
...