2017 October Release

How to Start the Fabasoft app.test PlayerPermanent link for this heading

Here it is described how you can start the Fabasoft app.test Player. Therefore, open the context menu of the test file (test, sequence, use case) to be executed in the "Projects" view and click "Run".

A dialog box opens where you can enter the properties for running a test in the Fabasoft app.test Player. Per default, these are set either to the general preferences of Fabasoft app.test (see chapter “Fabasoft app.test Preferences”) or to the properties of the project (or the test file). But you can change these settings in the input fields of the dialog box.

The dialog box is divided into four tabs:

  • "Run" tab
  • "Login" tab
  • "Agent" tab
  • "Reporting" tab

"Run" Tab of the "Run" DialogPermanent link for this heading

On the "Run" tab of the "Run" dialog you can define where the test/sequence/use case should be executed (web server, browser etc.) as well as additional information for running a test.

Field Name

Description

Application Type

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

  • HTML Page
  • Browser (Installed)
  • Mobile Browser
  • Java

Client Type

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

  • Microsoft Internet Explorer
  • Mozilla Firefox

When using the application type Browser (Installed) additionally the following client types are supported.

  • Google Chrome
  • Apple Safari

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 that this is only available when using the application type HTML Page as Fabasoft app.test doesn’t support different versions when using the installed browser for testing.

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. Again, this option is only supported for the application type HTML Page.

Details see “Multiple architecture support”.

Address

Specify 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 Web Server field by using {~webserver~}. This is the address the Fabasoft app.test Player connects to for running the test/sequence/use case.

{~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 into 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.

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.

On Error

Here 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 in the "Test State" view while a file is executed).
    • If you select "Break", the Fabasoft app.test Player stops the test run each time an error occurs and you have to continue the execution of the test by yourself.
    • 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 of the Fabasoft app.test Client Adaptor each time an error occurs. 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. This HTML file 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 (as a parameter table file) are saved. These files are referenced in the detailed report (see chapter “"Test Parameters" Tab”).
  • On Timeout Cancel
    If this check box is selected, the Fabasoft app.test Player stops the test run if a "Timeout" error occurs.

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 (see chapter “How to Add Breakpoints”).

  • 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.

Parameter Tables

In this field you can load one or more parameter table(s) for running the test file (see chapter “How to Create a Parameter Table File”).

Language Path

In this field you can define the path where the language files are located that are needed for running the test file (see chapter “How to Create Language Files”).

"Login" Tab of the "Run" DialogPermanent link for this heading

On the "Login" tab of the "Run" dialog you can specify how to log on to the web server specified on the "Run" tab.

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 (see chapter “Authentication Settings”).

Note: "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 a 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 (see chapter “How to Use Certificates in Fabasoft app.test”).

"Agent" Tab of the "Run" DialogPermanent link for this heading

On the "Agent" tab of the "Run" dialog you can define if the test/sequence/use case should be executed remotely at another computer.

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 a 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 is going to use.

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).

"Reporting" Tab of the "Run" DialogPermanent link for this heading

On the "Reporting" tab 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 Path

In this field you can enter the path of the folder where the report will be stored. If you specify a folder outside of the project, a linked folder will be created within the top level folder "Reports".

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 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.