Training Running Tests: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
== Background == | == Background == | ||
Device connection and STRIDE | Device connection and STRIDE test execution is handled by the [[STRIDE Runner]] (aka ''"the runner"''). The runner is a command line tool with a number of options for listing runnable items, executing tests, tracing on test points, and uploading your results. The runner is designed for use in both ad-hoc execution of tests and fully automated CI execution. The command line interface is sufficiently configurable to lend it to a variety of use-cases. You've already seen some basic test execution scenarios in the other training sections - now we will look explicitly at several of the common use cases for the runner. | ||
Please review the following reference articles before proceeding: | Please review the following reference articles before proceeding: | ||
Revision as of 21:22, 26 May 2010
Background
Device connection and STRIDE test execution is handled by the STRIDE Runner (aka "the runner"). The runner is a command line tool with a number of options for listing runnable items, executing tests, tracing on test points, and uploading your results. The runner is designed for use in both ad-hoc execution of tests and fully automated CI execution. The command line interface is sufficiently configurable to lend it to a variety of use-cases. You've already seen some basic test execution scenarios in the other training sections - now we will look explicitly at several of the common use cases for the runner.
Please review the following reference articles before proceeding:
Build a test app
List items
Trace on test points
with and without a filter...