Listing Functions and Test Units: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
* Verifying that a particular test unit is available in a specific build | * Verifying that a particular test unit is available in a specific build | ||
* Creating a command file that will be used to run only tests who's names match a specific text pattern | * Creating a command file that will be used to run only tests who's names match a specific text pattern | ||
* Creating a command file that will be used to run all tests in a particular order | |||
To list the available test units, run stride giving it command line parameters as follows: | To list the available test units, run stride giving it command line parameters as follows: | ||
Revision as of 00:22, 27 August 2009
While the STRIDE runner is mainly used to execute tests, it can also be used to list the test units that are available in a target build.
- Verifying that a particular test unit is available in a specific build
- Creating a command file that will be used to run only tests who's names match a specific text pattern
- Creating a command file that will be used to run all tests in a particular order
To list the available test units, run stride giving it command line parameters as follows:
stride --list --database TestApp.sidb