Running Tests (old): Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
Target-based [[Test Units]] are controlled by a | Target-based [[Test Units]] are controlled by a host computer, physically connected to the target via a configurable communication channel. | ||
== Prerequisites == | == Prerequisites == | ||
Revision as of 14:40, 16 April 2009
Overview
Target-based Test Units are controlled by a host computer, physically connected to the target via a configurable communication channel.
Prerequisites
In order to run target-based Test Units, the following prerequisites are required.
Host
- STRIDE Studio and its prerequisites installed on the host pc
- Host transport configured (see below)
Target
- Target transport configured
- TCP/IP over port 8000 is the default target transport. To apply other configurations, see SDKs
- Target built with STRIDE library built in and one or more test cases
- Target app running [1]
Host Transport Configuration
Host transport configuration is a one-time setup the comprises editing the transport.cfg file to reflect your target communication setup.
If you are using TCP/IP as your communcation channel, this configuration is typically only a matter of specifying your tareget's IP address (or DNS name) as the sockets DeviceAddress.
For configuration details, see Transport Configuration File.
Verifying Transport Settings
You can quickly verify your transport settings by running the Connect.pl script. (Installed to C:\STRIDE\Scripts\Connect.pl) (Your target must be running in order for the connection to succeed.)
Running Your Tests
Tests are executed on the target by running the script TestUnitRun.pl on the host computer.
Command line options allow you to tailor the the script's operation, but at a minimum:
- The script must be able to read the STRIDE database (.sidb) file that corresponds to the target build
- The script uses the transport configuration settings in transport.cfg to establish communication with the target
By default, tests are run in the order in which their corresponding SCL pragmas were seen by the STRIDE compiler (This can be overridden; see below.)
Examples
Commonly useful flags for TestUnitRun.pl include -v and -u. (See the link for complete information). For example:
Pre-Flight Testing
Useful for 'pre-flight' desktop testing, the following command line runs the target tests then automatically launches the local HTML report in your browser.
TestUnitRun.pl -d stride.db -v
Publication to Test Space
This example will run the target tests and then publish the results to STRIDE Test Space according to the configuration specified in your Test Spaces Configuration File.
TestUnitRun.pl -d stride.db -u -n="My Test Run"
Specifying Tests to Run
By default all tests are run in the order in which their corresponding SCL pragmas were seen by the STRIDE compiler. This is typically what you want, but you may also specify which test suites to run and in what order they are to be run.[2]
- Specify test(s) to run and their order on the TestUnitRun.pl command line (using -r)
- Specify test(s) to run and their order by means of an order file
Notes
- ↑ If target is multi-process, both the target and the STRIDE I/O daemon process must be started.
- ↑ A test suite here is the grouping of tests by SCL pragma; this corresponds to either:
- a test class
- #pragma scl_test_class()
- a set of free functions, or
- #pragma scl_test_flist()
- a C-based class)
- #pragma scl_test_cclass()
- a test class