In the configuration file you can define the properties for starting a test. The following XML tags are available:
The root tag of the configuration file is the <Config /> tag. In here you can define the path of the project in the attribute projectpath and the project name in the attribute projectname.
Note: If a backslash occurs in the end of a path you have to escape this backslash by another backslash (otherwise the backslash escapes the quotation mark).
Example |
<Config projectpath="D:\apptest-projects\Fabasoft Folio\\" > |
In the Run tag you can define the settings for running the test.
These are the attributes that can be set in the Run tag:
Example |
<Run |
In the BrowserSettings tag you can define if a proxy server should be used when connecting to the web site defined in the Run tag.
These are the attributes that can be set in the BrowserSettings tag:
Attribute | Description |
useproxy | In the useproxy attribute it is defined if a proxy server should be used. If this attribute is set to true a proxy server is used which also means you have to set the following attributes as well (for defining the proxy server to be used). Default value: false |
proxyserver | The proxyserver attribute defines the proxy server to be used (IP address or name). |
proxyport | In the proxyport attribute the port used by the proxy server is defined. Default value: 8080 |
jsenabled | In the jsenabled attribute it is defined if running JavaScript in the browser is enabled. Default value: true |
pluginsenabled | In the pluginsenabled attribute it is defined if running plug-ins in the browser is enabled. Default value: true |
Example |
<BrowserSettings |
You can define variables in the configuration that can be used in the test. There are two ways for defining parameter tables in the configuration file:
You can either load an existing function definition file by using the filename attribute or you can directly enter set statements into the ParameterTable tag.
If you use both, the parameters set directly in the configuration file (by set statements) overwrite the parameters from the file that is loaded.
Example |
<ParameterTable |
On the "Login" tab of the "Run" dialog the information for logging on is specified:
This information is also needed in the Fabasoft app.test Console Player and can be specified in the Login tag by setting the following attributes:
Attribute | Description |
authentication | In the authentication attribute you can define the type of authentication that should be used.
Default value: basic |
domain | The domain attribute specifies the domain of the user. This domain is overwritten if a domain is defined in a session of the test |
username | The username attribute contains the name of the user that should be used. This user is overwritten if a user is defined in a session of the test |
password | The password attribute contains the password that is used for logging on. This password is overwritten if a password is defined in a session of the test. |
Example |
<Login |
In the Adaptor tag you can define the properties for the Fabasoft app.test Client Adaptor like the size, the position and the port that should be used.
These are the attributes that can be set in the Adaptor tag:
Attribute | Description |
width | The width attribute defines the width of the Fabasoft app.test Client Adaptor (in pixels). Default value: 1000 |
height | The height attribute defines the height of the Fabasoft app.test Client Adaptor (in pixels). Default value: 750 |
poshor | The poshor attribute defines the horizontal position of the Fabasoft app.test Client Adaptor (in pixels). Default value: 10 |
posver | The posver attribute defines the vertical position of the Fabasoft app.test Client Adaptor (in pixels). Default value: 10 |
port | The port attribute defines the TCP port used by the Fabasoft app.test when running a test. Default value: 4360 |
Example |
<Adaptor |
In the TreeModel you can define the default tree model. If it is not set, the tree model is “ARIA”.
These are the attributes that can be set in the TreeModel tag:
Attribute | Description |
default | The default attribute defines the used tree model. Default value: ARIA |
<Telemetry ... />
In the Telemetry tag you can define if the Fabasoft app.telemetry should be started and used during the execution of a test file.
These are the attributes that can be set in the Telemetry tag:
Attribute | Description |
active | In the active attribute you can define if Fabasoft app.telemetry should be used. If you enter true into this attribute, Fabasoft app.telemetry is started when the test is started, too. Otherwise, the entries in the Telemetry element are ignored (which means the Fabasoft app.telemetry is not started). Default value: false |
username | The username attribute contains the name of the user that should be used for logging on to the Fabasoft app.telemetry server. |
password | The password attribute contains the password of the user that is defined in the user attribute. |
address | The address attribute contains the URL of the Fabasoft app.telemetry server. |
session | The session attribute defines the name of Fabasoft app.telemetry session (e.g. the name of the test that is carried out). With this name the telemetry session can be associated with a specific test run in the user interface of Fabasoft app.telemetry. |
target | The target attribute defines the target application that should be logged by Fabasoft app.telemetry, e.g. Fabasoft Folio. |
targetinstance | In the targetinstance attribute you can define an additional instance within the target application. This might for example be the domain id of the Fabasoft Folio domain. |
tier | The tier attribute defines the level at which Fabasoft app.telemetry should start following up the activities of the target. This might for example be the web service. The software telemetry follows up an activity that works on different level. |
tierinstance | In the tierinstance attribute you can define an additional instance of the starting level, for example an instance of the web service. |
level | The level attribute defines the logging level. Three levels are available within Fabasoft app.telemetry (details can be found in the documentation of Fabasoft app.telemetry):
|
filter | The filter attribute defines the context of the target application, for example a Fabasoft Folio user. This context is used to filter the activity that is followed up by Fabasoft app.telemetry. If no filter is specified, all activities of the product are monitored by Fabasoft app.telemetry. |
Example |
<Telemetry |