2017 October Release

Fabasoft app.test PreferencesPermanent link for this heading

In the Fabasoft app.test Preferences you can set the general preferences for Fabasoft app.test.

To define the general preferences, open the "Window" menu and select "Preferences".

A dialog box opens where you can enter the preferences. The Fabasoft app.test Preferences can be found in the "Fabasoft app.test" node and its subnodes:

  • "Agent" node
  • "Browser Settings" node
  • "Client Adaptor" node
  • "Login" node
  • "Mozilla Firefox" node
  • "Reporting" node
  • "Run" node
  • "Telemetry" node

"Fabasoft app.test" NodePermanent link for this heading

In the "Fabasoft app.test" node you can set general preferences for recording tests.

Field Name

Description

Replace Scope

If you select the Replace Scope check box, the scope entered in the Scope field ("Run" node) is replaced while recording. This means each time the scope is used within an execution it is replaced by the reference to the scope parameter ({~scope~}).
Note: The scope can be used for creating a test that can be executed parallel without using the same objects in different test runs.

Translate

If this check box is selected, the language strings that occur in the locations of executions are replaced by the references of the loaded language files in the Fabasoft app.test Click-Recorder.

Optimize Recorded Locations in Execution Statements

If this check box is selected, the path to the defined control used in execution statements is optimized which means elements that are not necessarily needed (e.g. CONTROLS) are left out in the location. This might possibly lead to errors if several controls exist with the same name.

Optimize Recorded Locations in Set Statements

If this check box is selected, the path to the defined control used in set statements is optimized.

"Agent" NodePermanent link for this heading

In the "Agent" node you can define if the Fabasoft app.test Agent should be used for remote testing or not.

Field Name

Description

Host Name

In this field the host name of the computer is entered where the Fabasoft app.test Agent is installed (which means you want to run a test remotely at another computer). If you are not using remote connection, type localhost into this field.

Port

In this field the TCP-port is entered that should be used if you connect remotely to another computer. This is the TCP-port the Fabasoft app.test Agent will use. The default port is 5024.

Transfer Documents

If you test remote at another computer, the documents that are imported (or the folders, where they are exported to) might not exist on the remote computer. Therefore, select this check box for transferring all needed documents from the Fabasoft app.test Studio to the Fabasoft app.test Agent (and the other way round).

"Browser Settings" NodePermanent link for this heading

In the "Browser Settings" node you can define if a proxy server should be used and if JavaScript or Plug-ins should be enabled.

  • Use Proxy
    Select this check box if you want to use a proxy server for connecting to the web site defined in the "Run" node.
  • Proxy Server
    In this field you define the proxy server to be used (if the check box Use Proxy has been selected).
  • Proxy Port
    Enter the port used by the proxy server into this field.
  • Enable JavaScript
    Select this check box if you want to enable running JavaScript in the browser (default is enabled).
  • Enable Plug-ins
    Select this check box if you want to enable running Plug-ins in the browser (default is enabled). Please note that this preference is independent of the setting of "Enable Mozilla Folio Plug-ins" in the "Mozilla Firefox" Node.

Note: As you cannot define a user, integrated authentication is used for connecting to the proxy server which means the currenty logged-on user id used.

"Client Adaptor" NodePermanent link for this heading

In the "Client Adaptor" node the preferences for the Fabasoft app.test Client Adaptor are defined (such as its size or its position).

Field Name

Description

Width

In this field you can define the width of the Fabasoft app.test Client Adaptor (in pixel).

Height

In this field you can define the height of the Fabasoft app.test Client Adaptor (in pixel).

Horizontal Position

In this field you can define the horizontal position of the Fabasoft app.test Client Adaptor (in pixel).

Vertical Position

In this field you can define the vertical position of the Fabasoft app.test Client Adaptor (in pixel).

Port

This field contains the TCP-port used by the Fabasoft app.test Client Adaptor.

"Login" NodePermanent link for this heading

In the "Login" node you can define the preferences for logging on to the web server to be tested.

Field Name

Description

Start Application

This field defines the mode that should be used for logging on to the server. For using the specified mode the prerequisites must be fulfilled.
"Run As {~domain~}\{~username~}:{~password~}" is only possible within a Microsoft Windows environment (and not at an Ubuntu client).

{~domain~}

This field defines the domain for which the user is authenticated. This domain is overwritten if a domain is defined in a sequence of the test

{~username~}

In this field you can enter the user that should be used for connecting to Fabasoft Folio, Mindbreeze Enterprise Search or Liferay Portal. This user is overwritten if a user is defined in a sequence of the test.

{~password~}

This field indicates the password for the specified user to log on. This password is overwritten if a password is defined in a sequence of the test

Certificate

In this field you can define if a certificate should be used when connecting to the web server. Enter the path and/or the name of the certificate into this field (if a certificate should be used).

"Mozilla Firefox" NodePermanent link for this heading

In the "Mozilla Firefox" node you define the properties for using Mozilla Firefox for testing.

Field Name

Description

Start Application: Allow Kerberos

This check box must be selected if you use Kerberos authentication with Mozilla Firefox. If you do not use Kerberos authentication, clear the check box.

Start Application: Enable Mozilla Folio Plug-ins

This check box must be selected if you want to enable the Folio Plug-ins delivered with Fabasoft app.test. Please note that this preference is independent of the setting of "Enable Plug-ins" in the "Browser Settings" Node.

"Reporting" NodePermanent link for this heading

In the "Reporting" node you define the preferences for creating a report when a test/sequence/use case is executed in the Fabasoft app.test Player.

Field Name

Description

Report Name

In this field you can enter the name of the report to be generated. Each time a test, sequence or use case is executed in the Fabasoft app.test Player (or the Fabasoft app.test Console Player) a report is created in which the result of the test run (which statements have been carried out successfully and which have thrown an error) is documented. If the report should have the same name as the test itself, you can reference the name of the test by using {~testname~}. Additionally, you can use the scope, which has been defined at the "Run" node, by using {~scope~}. Furthermore, you can use the parameter timestamp (whose value is created based on the current date and the current time) and sleep ("Run" node).

Environment Information - can only be found in the XML file of the report and not in the HTML view.

Database Environment

Here you can enter the type of the database that is used.

Backend Environment

Here you can enter the environment details (e.g. the operating system) where the Fabasoft Folio backend services are running.

Conversion Environment

Here you can enter the name of the operating system where the Fabasoft Folio conversion service is running.

Web Server Environment

Here you can enter the name of the operating system where the Fabasoft Folio web server is installed.

Client Environment

Here you can enter the name of the operating system of the computer running Fabasoft app.test.

"Run" NodePermanent link for this heading

In the "Run" node you define the general preferences for starting the Fabasoft app.test Recorder or the Fabasoft app.test Player.

Field Name

Description

Application Type

This field contains the type of application that should be started for recording or running a test, sequence or use case. The following application types are available:

  • HTML Page
  • Browser (Installed)
  • Mobile Browser

Client Type

This field contains the type of client that should be started for recording or running a test, sequence or use case. The following client types are available:

  • Microsoft Internet Explorer
  • Mozilla Firefox

The application type Mobile Browser currently supports the following client types.

  • Google Chrome

Client Version

If "Mozilla Firefox" has been selected in the Client Type field, the version of Mozilla Firefox that should be used for testing can be selected in this field.

Note: The tested client (e.g. Fabasoft Folio) might not support each of these Mozilla Firefox versions.

Architecture

This field defines the architecture of the launched app.test Adaptor process.
For details see chapter “Report Log Style”.

Address

Enter the address of the Fabasoft Folio domain, Mindbreeze Enterprise Search query service or Liferay Portal to be tested in this field. You can reference the entry of the Web Server field by using {~webserver~}. This is the address Fabasoft app.test is connected to for recording and running tests.

{~webserver~}

Enter the host name of the Fabasoft Folio domain, Mindbreeze Enterprise Search query service or Liferay Portal in this field.

{~scope~}

Enter a scope in this field. This scope can be used for creating a test that can be executed parallel on the same system without using the same objects in each test run. The scope is a number from 1 to 9999. If you use the scope for naming and using objects, you can run a test parallel by using a different scope in each test run

Runs

This field specifies how often a test, a sequence or a use case should be carried out in the Fabasoft app.test Player.

Sleep

Use this field to define how long the Fabasoft app.test Player should wait between two statements. The delay is entered in milliseconds. Please note that any value higher than zero makes the execution of a test, sequence or use case slower.

Execution Timeout

The default timeout of Fabasoft app.test is 30 seconds (30000 ms). This means an execution statement is NOK if it does not finish after the defined timeout. You can change the timeout value by changing the value in this field. You can overwrite this value for each project and each test as well as for single statements (see chapter “Enhance a Test by Adapting the Timing”).

Sequence Timeout

The default sequence timeout of Fabasoft app.test is 2 times the default execution timeout (will be calculated if not defined, defaults to 1 minute (60000 ms)). This means a sequence statement is NOK if it does not finish starting after the defined timeout. You can change the timeout value by changing the value in this field. You can overwrite this value for each project and each test as well as for single statements (see chapter “Enhance a Test by Adapting the Timing”).

Context
Timeout

The default context timeout of Fabasoft app.test is 3 times the default execution timeout (will be calculated if not defined, defaults to 90 seconds (90000 ms)). This means a context statement is NOK if it does not finish starting after the defined timeout. You can change the timeout value by changing the value in this field. You can overwrite this value for each project and each test as well as for single statements (see chapter “Enhance a Test by Adapting the Timing”).

On Error

In this field you can define how the Fabasoft app.test Player should react when an error occurs.

  • In the select box you can define what should happen if an error occurs (this setting can also be changed while a file is executed).
    • If you select "Break", the Fabasoft app.test Player stops the execution each time an error occurs and you have to continue the execution of the test manually.
    • If you select "Continue", the Fabasoft app.test Player carries out the next statement after the error, i.e. the error is ignored. You can view the errors that occurred later on in the report.
    • If "Cancel" is selected the execution of the file stops completely if an error occurs.
  • Screenshot
    If this check box is selected, a screenshot is taken from the Fabasoft app.test Client Adaptor each time an error occurs in the Fabasoft app.test Player. This screenshot is referenced in the detailed report that is created after the test run.
  • HTML Dump
    If this check box is selected, the HTML of the currently shown site in the Fabasoft app.test Client Adaptor is saved each time an error occurs in the Fabasoft app.test Player. This HTML is referenced in the detailed report.
  • Control Tree Dump
    If this check box is selected, the current control tree (XML file) as well as the currently set test parameters (parameter table) are saved. These files are referenced in the detailed report.
  • On Timeout Cancel
    If this check box is selected, the Fabasoft app.test Player stops the test run if a "Timeout" error occurs.

Max.Errors per Test

In this field you can define the number of errors after which a test should be cancelled. This means that the test is stopped if this number of errors is exceeded.

Max.Errors per Sequence

In this field you can define the number of errors after which a sequence should be cancelled. This means that the sequence is stopped and the next one is started if this number of errors is exceeded.

On Breakpoint

In this field you can define if the Fabasoft app.test Player should stop if a breakpoint is reached. Breakpoints might be added within the Fabasoft app.test Recorder.

  • If you select "Break" the Fabasoft app.test Player stops each time a breakpoint is reached.
  • If "Continue" is selected, breakpoints are ignored and the Fabasoft app.test Player does not stop if a breakpoint occurs.

Language Files

In this field you can define the path where the language files are located that should be used in Fabasoft app.test. You can also change this path when starting the Fabasoft app.test Recorder resp. Player.

"Telemetry" NodePermanent link for this heading

In the "Telemetry" node you can define if an Fabasoft app.telemetry session should be started when a test is executed in the Fabasoft app.test Player.

The following fields can be set:

Field

Description

Activate

If the Activate check box is selected, a Fabasoft app.telemetry session is started with each test run in the Fabasoft app.test Player.

Telemetry Server

Address

In the Address field the URL of the Fabasoft app.telemetry server is entered.

Username

In the Username field you enter the name of the user that should be used for logging on to the Fabasoft app.telemetry server.

Password

The Password field should contain the password of the user that is defined in the Username field.

Telemetry Session

Session

Enter the name of the Fabasoft app.telemetry session into the Session field (e.g. the name of the test that is carried out). With this name the telemetry session can be associated with a specific test execution in the user interface of Fabasoft app.telemetry.

Target

In the Target field the target application that should be logged by Fabasoft app.telemetry is defined, e.g. Fabasoft Folio Compliance.

Target Instance

In the Target Instance field 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 field 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.

Tier Instance

In the Tier Instance field you can define an additional instance of the starting level, for example an instance of the web service.

Filter

The value in the Filter field 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.

Level

The Level attribute field defines the logging level. Three levels are available within Fabasoft app.telemetry (details can be found in the documentation of Fabasoft app.telemetry):

  • STANDARD
  • DETAIL
  • DEBUG

If a valid Fabasoft app.telemetry server has been defined in the Server area, the corresponding values of this server are loaded into fields in the Session area which means they can be selected in the drop-down menu.

Properties of a Fabasoft app.test ProjectPermanent link for this heading

You can also set individual properties for each project (as well as for each test file) by opening the context menu in the "Projects" view and clicking "Properties".

A dialog box opens where you can set the same properties as in the general preferences (except the preferences that are set for the whole Fabasoft app.test Studio).