2017 October Release

How to start the Fabasoft app.test RecorderPermanent link for this heading

Here it is described how you can start the Fabasoft app.test Recorder. Therefore, you have to open a test (or a sequence or a use case) by double clicking it in the "Projects" view.

The test file is opened and you can click "Start/Stop Recorder" in the "Outline" view.

A dialog box opens where you can enter the properties for starting the Fabasoft app.test Recorder. 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 in several tabs.

"Run" Tab of the "Start Recorder" dialogPermanent link for this heading

On the "Run" tab of the "Start Recorder" dialog you can define where the test/sequence/use case should be recorded (web server, browser etc.) as well as the path where the language files are located for translating the test.

Field Name

Description

Application Type

This field contains the type of application that should be started for recording a 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 recording a 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 entry in the Web Server field by using {~webserver~}. This is the address the Fabasoft app.test Recorder connects to for recording 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 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. If you have selected that the scope should be replaced while recording in the Fabasoft app.test Preferences (see chapter “Fabasoft app.test Preferences”), it is replaced by the reference to the scope parameter each time it occurs in a location (e.g. when naming an object).

Language Path

In this field you can define the path where the language files are located that should be used for recording.

"Login" Tab of the "Start Recorder" dialogPermanent link for this heading

On the "Login" tab of the "Start Recorder" 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 (see chapter “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 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. You can define a path and/or a name. If no path is defined the "Certificates" folder of the current project is used. If no name is defined, Fabasoft app.test searches for a certificate with the name of the user entered into the {~username~} field (see chapter: “How to Use Certificates in Fabasoft app.test”).

"Agent" Tab of the "Start Recorder" dialogPermanent link for this heading

On the "Agent" tab of the "Start Recorder" dialog you can define if the test/sequence/use case should be recorded remote 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 record 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).

"Migration" Tab of the "Start Recorder" dialogPermanent link for this heading

On the "Migration" tab of the "Start Recorder" dialog you can define if locations should be automatically migrated while interpreting the test in the context of this recorder session.

Field Name

Description

Migrate during debugging

If this check box is checked, locations will be automatically migrated while the test runs in the context of this recorder session.

Migration

Select one of the well known migration declarations.

Start the Fabasoft app.test RecorderPermanent link for this heading

If you have finished defining the properties for starting the Fabasoft app.test Recorder, you can save these settings by clicking the "Set as default" button. In that case the entered properties are saved for this single test file.

By clicking "OK" you can start the Fabasoft app.test Recorder.

If you click "Cancel" (or "Close" if you have saved the properties before), the "Start Recorder" dialog is closed and the Fabasoft app.test Recorder is not started.

When the Fabasoft app.test Recorder is started, the Fabasoft app.test Client Adaptor opens. In this window the tested web site is embedded.

All controls displayed in this Fabasoft app.test Client Adaptor are shown in the Fabasoft app.test Studio too within the control tree. This control tree is shown in the "Editor Area" view.

This control tree can be used for recording statements (see chapter “How to Record a Test using the Control Tree”).

In the "Editor Area" view you can find all information needed for recording test (divided in tabs). These tabs are:

  • Recorder - here you can find the control tree mentioned above
  • Source - here the source code of the test file is shown
  • Test Parameters - here you can find all parameters set within the test by the user
  • System Parameters - here you can find a list of all parameters set by the system
  • Translation Table - here you can find a list of all language key/value pairs loaded from language files (when translating a test during recording).
  • The other way of recording a test is to record the statements in the Fabasoft app.test Click-Recorder.