Test Script: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Stride's test script solution allows users to take advantage of the power of dynamic languages on the host to execute test scenarios on the device under test. Some of the adva...") |
|||
Line 31: | Line 31: | ||
== Running a Test Script == | == Running a Test Script == | ||
Stride executes tests using a runner controlled by a host computer. Refer to [[ | Stride executes tests using a runner controlled by a host computer. Refer to [[Running Tests]] for Test Units. | ||
'''Invoking the Runner (aka <tt>[[STRIDE_Runner|stride]]</tt>) from a console''' | '''Invoking the Runner (aka <tt>[[STRIDE_Runner|stride]]</tt>) from a console''' | ||
stride .. --run=MyTest.pm | stride .. --run=MyTest.pm |
Latest revision as of 20:46, 6 July 2015
Stride's test script solution allows users to take advantage of the power of dynamic languages on the host to execute test scenarios on the device under test. Some of the advantages of host based script tests are:
- test coverage can be expanded without any changes to the target device.
- sophisticated device automation possible using facilities available on the host.
- no additional code space requirements on the device once the software under test.
- powerful data validation techniques are possible using the power of the host (validating large media files generated by the target device, for example).
- large library of extension modules are available for standard dynamic languages (e.g. cpan for perl)
Example Test Script (i.e. MyTest.pm)
use strict;
use warnings;
package MyTests;
use base qw(STRIDE::Test);
use STRIDE::Test;
sub test_one : Test
{
ASSERT_TRUE(1);
}
sub test_two : Test
{
ASSERT_TRUE(0);
}
1;
Running a Test Script
Stride executes tests using a runner controlled by a host computer. Refer to Running Tests for Test Units.
Invoking the Runner (aka stride) from a console
stride .. --run=MyTest.pm