Configuring TestDriver using command-line options
Configuring TestDriver using the
You can view or modify these settings using appropriate option of
To configure TestDriver using Carbide, refer to Configuring using Carbide
The following settings are made to configure the TestDriver using the
Setting the epoc driveTo set the EPOC drive, use the command:
For example, Setting the root path to XML structureTo set the root path to your XML structure, use the command:
For example, Setting the root path to repositoryTo set the root path to the repository:
For example:
Setting the root path to test resultsTo set the root path to the test results, use the following command:
This is used to set the root path for the test results and test logs. Setting the root path to source codeTo set the root path to the source code, use the following command:
TestDriver enables you to set more than one option using the
After configuring TestDriver, you can start using it. For more options, see config. Setting entry point address field
To tell the TestDriver the task it has to run, set the entry point
address field, this is the task that TestDriver has to run. This value
is set using You can set the entry point field in the following ways:
Note: You can completely configure the TestDriver, this
includes setting the entry point address, setting for build and so on using
' Configuring the plug-insTestDriver enables you to configure the plug-ins that are installed with it. These plug-ins are installed with default settings, which can be customised later.
You can change the default settings using the
For example, the following command sets the portNum variable of the reflash plug-in to 3:
Configuring logging information
TestDriver uses the
An example for the
Configuring the logging information involves setting up the following in
the Logging levels
A logging level can be used to control the logging output. A log
message can be differentiated by it's level that can be configured by editing
the line containing The supported logging levels in descending order are:
Enabling logging at a given level also enables logging at all higher
levels. For example, when you set Logging handlersHandlers enable you to output logs to different locations such as a console, a file, a stream, memory, or a TCP socket on a remote host. Multiple handlers are used to output to each of these locations (for example, print all log messages to a file or to the console). Handlers include standard Java Handlers, including FileHandler, ConsoleHandler, MemoryHandler, StreamHandler and SocketHandler. However, Symbian also provides two custom handlers, EmailHandler and NetSendHandler that enable you to output logging messages to an email address and NetSend location respectively.
You can configure the log message to a handler using the
For example:
This sets up the Example for handlersIn the following example:
The Example of the possible properties configurations for these handlers are as follows:
This sets the maximum number of errors that can occur before sending an email.
This sets the meaning of the error.
This sets the IP address to send the net-send message.
This sets the maximum number of errors that can occur before sending an email.
This sets the meaning of the error.
The address from where the log messages have to be sent.
The address to send the log messages.
The SMTP server to send the log messages. Output Formatters
Log messages can be sent to locations stated in the
Logging Handlers section, as either in a
simple text or in an XML format. Output formatters enable you to organise your
output. Java includes the standard formatters, More information on configuring the properties file to set the logging levels, handlers and formatters can be found in Configuring the logging properties and Logging messages.
Copyright ©2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: SFL
|