After building a test, the resulting binaries and the data files are
collected in a repository. The path to the repository is defined when
configuring the TestDriver, for details, see Configuring TestDriver. The repository
structure also represents the test hierarchy.
Test structure within a repository
The test structure of the repository would be in this form:
${repositoryRoot}/${buildNumber}/${platform}/${build}/${xmlTree}
where:
-
REPOSITORY_ROOT_FOLDER
is the location of the
repository specified by the command testdriver config –-repos
-
BUILD_NUMBER
is calculated depending on your epocroot
specified by the command testdriver config –e
-
PLATFORM
is the platform specified in any command
using the option -p
(ARM4/WINS/WINSCW/THUMB
)
-
BUILD
is the build specified anywhere using the option
-b
(UDEB/ UREL
)
-
XML Tree
is the tree structure of your Driver file
organised by tasks.
The followin illustration is an example of a repository constructed as
a result of building systemtest.st_security winscw urel
.
After the running the test, the output file is copied to the repository
following the standard hierarchy of files:
${repository_dir}\${build_number}\${suite_name}\${test_name}.test.log
.
While a test is being executed, the log file, is temporarily stored in
a location which is determined in the following order:
-
extra optional parameter in the run command using the option
-l
-
optional parameter in TestDriver preferences in the configuration
file ("Log")
-
c:\test.log
The -l
switch is used to specify the location to save the
RTests and the RDebug logs. Specifiy the comm port to be connected to the
RDebug port on the PC, the RDebug or the RTest output are routed through this
port. For example, testdriver run -l comm1
where, comm1 is the
RDebug or RTests port.
Specify the complete location either in the command line or in the
(configuration file) preferences, for example, "c:\directory
" is
interpreted as a file directory
in C:\
.