2017 June Release

Error Messages in Fabasoft app.testPermanent link for this heading

Here you will find a list of all error messages that might occur in Fabasoft app.test when recording or running tests as well as descriptions and possible solutions to the problem.

[1001] Control not found: There is no <control> in <path>

The error message "There is no <control> in <path>" tells you that the control, where you wanted to perform an execution or a set statement, does not exist on the currently shown site (e.g. if you try clicking the "Next" branch even though it is not shown).

In these cases the error message "There is no <control> in <path>" might occur:

  • The location in your execution/set statement might be wrong (typing mistakes, wrong PAGE, ...).
  • Something might be wrong in the tested system so that the control is not shown.
  • These are some ways for identifying the problem why this error message occurred:
    • When executing the test in the Fabasoft app.test Player, create screenshots, a dump of the currently shown HTML page as well as a dump of the control tree of Fabasoft app.test. These files can be used for identifying why the error occurred.
      • Screenshot: Open the screenshot to check if the control is shown.
      • HTML dump: Check if the control exists in the HTML page.
      • Control tree: Check if the control is listed in the control tree.
    • If the error occurred when running a test in the Fabasoft app.test Player, execute the test in the Fabasoft app.test Recorder, too. So you can use the control tree for checking if the correct location is used.

[1010] Repaired adaptor state: <message>

The error [1010] Repaired adaptor state: Page/overlay primarily not found, but succeeded (<performed actions>). is shown when a control not found error occured, but the state of the adaptor could be repaired (overlays which could prevent app.test to find the control and execute the action on it could be closed and the execution succeeded after this).

The error [1011] Repaired adaptor state: <performed actions>, but failed with <error message>. is shown when a control not found error occured and overlays which could prevent app.test to find the control and execute the action on it could be closed (the page in the location is open, but was not on top), but after this the execution still failed.

[1101] Timeout @ <error occurrence>

The "Timeout" error occurs if an execution (set statement, validation, ...) takes too long for being executed. The default timeout in Fabasoft app.test is 30 seconds (30000 ms).

Possible reasons:

  • The browser took too long for performing an action.
  • The web server did not send a response.

Possible solutions:

  • Use waitafter or waitbefore
    For each execution statement you can define a time (im ms) the Fabasoft app.test Player should wait before or after this execution. Therefore, the attributes waitbefore and waitafter are available. If you set waitafter of an execution for example to 40000 ms, the Fabasoft app.test Player waits 40 seconds after the execution has been carried out till the next statement is executed. The waitbefore or waitafter value is only valid for one statement.
    You can define this in the advanced properties of the execution (by selecting the statement in the "Outline" view).
    You can also set this attributes directly in the source code of the test file:
    <Execution action="<action>" location="<location>" waitafter="<time in ms>" waitbefore="<time in ms>" />
  • Change general timeout
    Before starting a test you can change the general timeout of Fabasoft app.test. The default execution timeout is 30000 ms (30 seconds), the default timeout for starting a sequence 60000 ms (1 minute) and the default timeout for starting a context 90000 ms (1 minute 30 seconds). You can change the general timeout in the preferences of the Fabasoft app.test Studio. Therefore, open the "Window" menu and select "Preferences". Change to the "Run" node (in the "Fabasoft app.test" node). In the Execution Timeout, Sequence Timeout and Context Timeout fields you can enter the appropriate timeout in milliseconds. This timeout is valid for each appropriate execution of a test file within the Fabasoft app.test Studio (if it is not overwritten by a specific timeout within a statement).
    If you run a test in the Fabasoft app.test Console Player you can define the timeout value in the configuration file. Therefore, the attribute timeout in the <Run /> tag is available.
  • Change timeout for statement
    Furthermore, you can define a timeout just for one statement (execution, context switch, sequence). If you know for example that an execution might last longer than the defined timeout, you can define an individual timeout only for this single statement.
    Note: If you define a timeout for a context switch, this is only taken for switching to the new context (e.g. if you know that a window might take longer to be opened). When a timeout is defined for a sequence it is also taken only for starting the sequence (and not for all statements within the sequence).

[1201] Unexpected HTML: <message>

This error occurs if app.test tries to execute an action, but the HTML is not as expected. This should usually never occur in typical test execution.

[1301] Control is disabled @ <element>

If you try clicking a button that is disabled, the following error is displayed:

Example

<Execution action="Click" location="PAGES.Explore.BUTTONBAR.Destroy" />

[1302] Control: Value not found @ <class>

If you try setting a select box to a value that does not exist, the error "Value not found" is displayed.

Example

<Execution action="Set" location="PAGES.Explore.Address[0].Topic" value="Temporary" />

[1303] Menu not found

This error is displayed when Fabasoft app.test waits for a menu to appear, but it cannot be found within the given timeout.

[1304] Keypress: no active element to fire event to.

This error occurs when the browser does not indicate any HTML element to be the active element to fire the key events to. The error will only be displayed when testing against Folio versions < 11.

[1501] Drag and Drop: <error message>

This error occurs when e.g. app.test could not find a target to perform a Drag&Drop event for importing a document or a general error occurs while performing Drag&Drop actions.

[1601] Open Context: <error message>

These error messages might occur when executing a context switch:

  • No lock registration for "<document>"
  • No unlocked window matches sufficiently for "<document>"
  • No matching window found

[1601] Open Context: No lock registration for "<document>"

If you execute a context switch (with the option "Locked"), the following error message might appear:

No lock registration for "<document>" (locked) after xx seconds"

This error message tells you that the document, the context should be switched to, cannot be found within the defined timeout. This might have the following reasons:

  • The location (name of the document) defined in the context switch is not exactly the same name as the opened object has.
  • Opening the document has taken longer than the timeout that has been defined.
  • The document is opened in reading mode and so it is not locked by the Fabasoft Components Web Control Tool Manager.

These may be possible solutions:

  • If the document is not opened in editing mode, do not use the option "Locked".
  • Check if you have used the correct location (object name) in the context switch. Therefore, open the Fabasoft Tracer, in which you can find the name of the document Fabasoft app.test is looking for.
  • Change the timeout of the context switch if it takes longer than the defined default timeout to open the object. Therefore, select the context switch in the "Outline" view and change to the "Properties" view. Switch on the "Advanced Properties". Enter the timeout value into the Timeout field. This timeout is only valid for switching the context - not for the statements within the context switch.

[1601] Open Context: No unlocked window matches sufficiently for "<document>" (not locked)

If you execute a context switch, the following error message might appear:

No unlocked window matches sufficiently for "<document>" (not locked) after xx seconds"

This error message tells you that the unlocked document, the context should be switched to, cannot be found within the defined timeout. This might have the following reasons:

  • The location (name of the document) defined in the context switch is not exactly the same name as the opened object has.
  • Opening the document has taken longer than the timeout that has been defined.

These may be possible solutions:

  • Check if you have used the correct location (object name) in the context switch. Therefore, open the Fabasoft Tracer, in which you can find the name of the document Fabasoft app.test is looking for.
  • Change the timeout of the context switch if it takes longer than the defined default timeout to open the document. Therefore, select the context switch in the "Outline" view and change to the "Properties" view. Switch in the "Advanced Properties". Enter the timeout value into the Timeout field. This timeout is only valid for switching the context - not for the statements within the context switch.

[1601] Open Context: No matching window found

This error is thrown if no matching window has been found for the context (no matter if the document searched for should be locked or unlocked). This error message mostly appears within an Ubuntu environment.

[1603] Close error: Last browser may not be closed

A "Close Error" is thrown if problems occur when closing a window, e.g. when trying to close the last browser window, which is not possible within a Fabasoft app.test test.

[1611] File dialog: <error message>

This error is displayed when there is a problem handling a file dialog (import and export actions), e.g. if the dialog could not be found.

[1701] Client error: <error message>

This error tells you that an unexpected error occured in the tested Fabasoft Folio domain.

If this error is expected to occur you can define this in your test.

Otherwise, check why this client error occurred and then either adapt the test (if the test is incomplete) or fix the problem in the Fabasoft Folio domain.

A Client Error also occurs, if Fabasoft Folio reports an error internally via a defined JavaScript interface to Fabasoft app.test.

[1702] Client Error: Script Error: <error message>

This error is displayed if a script error occurs. Note that a sequence is not aborted, if a script error occurs on startup.

[1801] Download not complete: <error message>

This error occurs if executing a file download (e.g. exporting a document, option: save) fails.
The download fails if the file cannot be found in the file system, it still changes after exceeding the execution timeout or the download target folder could not be created.

[1901] Invalid operation: Operation currently not available

This error is displayed when e.g. performing a Back or Forward action on a WINDOW in the generic HTML connector, but the action is currently not available as there is no page in the history to navigate to.

[1902] The current test has been aborted

This error is thrown when the test has beeen aborted due to e.g. too many errors, a fatal error which prevents further execution within the test or a failed assertion which cancels the test.

[1903] The current sequence has been aborted

This error is thrown when the sequence has beeen aborted due to e.g. too many errors, a fatal error which prevents further execution within the sequence or a failed assertion which cancels the sequence.

[2001] Invalid control specification: <error message>

This error occurs if there is a problem setting a control specification, e.g. if there is a syntax error or the Fabasoft app.test Adaptor is not able to apply the control specification.

[2002] Invalid xpath expression: <error message>

This error occurs if there is a problem evaluating an XPath expression within a control specification, e.g. if there is a syntax error or the result type of the expression cannot be used to continue processing in the appropriate context.

[2003] Invalid javascript expression: <error message>

This error occurs if there is a problem evaluating a JavaScipt expression within a control specification, e.g. if there is a syntax error, an exception occurs or the result type of the expression cannot be used to continue processing in the appropriate context.

[2004] Unsupported language: <language>

This error occurs if there is an attempt to use an expression language in a control specification which is not supported. Currently XPath and JavaScript are supported languages.

[3001] Invalid statement: <error message>

The "Invalid statement" error is thrown if there is an error in the statement, for example if an attribute is missing.

[3001] Invalid statement: Missing attribute 'parameter'

This error message tells you that Fabasoft app.test tried executing a set statement where no parameter name is defined.

Example

<Set location="PAGES.Explore.Object List[0]" />
<!-- missing: parameter="parametername" -->

[3001] Invalid statement: Invalid Execution Statement

The "Invalid Execution Statement" error tells you that there is a mistake in your execution statement, e.g. if you did not define an action.

Example

<Execution location="MENU.New" />
<!-- missing: action="Click" -->

[3002] Invalid attribute: Invalid value @ <class>

This error in thrown if an attribute contains an invalid value

Example

<Exection action="Keypress" location="WINDOWS[LAST]" value="EnterKey" />
<!-- should be: value="ReturnKey" -->

[3001] Invalid statement: <error message>

The "Invalid statement" error is thrown if there is an error in the statement, for example if an attribute is missing.

[3101] Invalid location syntax: <error message>

There is a syntax error in the location.

[3201] Invalid location syntax: <error message>

The result type of an expression (e.g. named index access in lists) inside of a location is invalid.

[3201] Command not supported: <action> @ <controltype>

This error message is shown if you try to execute an action on a control where this action is not allowed (e.g. if you try setting a value into a READONLY field).

Following some reasons are described, why this error might occur:

  • If the location is not fully qualified and two controls with the same name exist on the web page, it might happen that the wrong control is found.
    Example The "Name" control exists on both pages. If you use "Name" in your location (instead of a fully qualified location), the first control with the name "Name" is used. In this example this is the folder from the tree on the first page and not the input field on the second page - and the folder does not support the action "Set". This can be solved by using fully qualified locations (PAGES[1].CONTROLS.Name).
  • The control has another type than expected (e.g. it is a read-only field instead of an input field).
  • You might use a wrong location (e.g. a typing mistake in the location if you have added/changed the location in the source code).

[3203] File download dialog not supported on this platform @ <element>

In an Ubuntu environment the handling of dialogs is not supported by Fabasoft app.test if not using Firefox >= 10.0. Therefore, an error occurs if you try exporting a file in a test on an Ubuntu platform with older Firefox versions.

[3204] File upload dialog not supported on this platform @ <element>

This error is reported if the file upload dialog cannot be handled on the appropriate platform. It is currently supported on all supported Windows Browsers and Firefox >= 10.0 on Linux.

[3205] Uploading an empty file is not supported in Firefox version <= 8.0

Uploading an empty file (file size: 0 bytes) with a Firefox version <= 8.0 is not supported.

[3301] Syntax error: Error at expression position x

A syntax error occurs if there is a mistake in the syntax of your statement.

These are some examples where Fabasoft app.test shows this error:

  • Typing error in the tag name
  • Typing error in the evaluation of a set statement

Example

<Exection action="Click" location="Desktop" />
<!-- should be: <Execution... /> -->

<Set parameter="ButtonExists" location="Next" eval="Exist" /> <!-- should be: eval="Exists" -->
<Set parameter="SplitString" eval='SplitLeft("MyString", )' />
<!-- should be: eval='SplitLeft("MyString", "S")' -->

[3302] Unbalanced parenthesis: <error message>

If the count of opening/closing parenthesis in an expression is unbalanced, this error is displayed.

[3303] Unbalanced string delimiter: <error message>

If you forgot a string delimiter - which means a quotation mark - this error is displayed.

Example

<Execution action="Click location='Object List["Name"=="{~FolderName~}]' />
<!-- should be: Object List["Name"=="{~FolderName~}"] -->

[3304] Parser Action Error: <error message>

This error occurs if the expression parser needs to execute an action (e.g. a GET action for the location in a Set-Statement) and it fails.

[3306] Division by zero: <error message>

This error tells that in a statement you try to divide a value by zero (e.g. in a set statement).

<Set parameter="Division eval="8/(2-2)" />

[3401] File not found: [<file path>]

If you try importing a file that does not exist in the defined folder, a "File not found" error is displayed. The path, where the file was searched, can be found in the error message.

[3501] Parameter: System parameters (like "<parameter>") must not be changed by a <Set> statement

This error occurs if you try to change a system parameter in a test. System parameters are provided by app.test and cannot be changed with Set-Statements.

[4001] Validation failed: <error message>

This error occurs if a validation went wrong in your test.

This error is dispayed in the syntax

[4001] Validation failed: (<wrong validation>)==false

These are the reasons why the "validation failed" error might occur:

  • A validation statement went wrong, e.g.
    <Validation ok="{~CountRows~}==6" />
  • An expected error did not occur when running a test.
    <Execution action="Click" location="Next" ok="Error" />

[4002] Assertion failed: <error message>

This error is reported when an assertion statment fails. Details see “Assert Statement”.

[5001] Clarification required: <error message>

This indicates an internal error which may e.g. occur if Fabasoft app.test crashes or runs into an invalid state.

[5001] Clarification required: Another action in progress

This error says that the last action has not yet finished. This might happen if the last execution statement ran into a timeout and the next execution should already be carried out even though the has not completed.

[5002] Unknown host: <hostname>

This error indicates that the IP address of the used Fabasoft app.test Agent host name could not be determined.

[5003] Connection Error: <errormessage>

This error occurs if Fabasoft app.test loses the connection to the web server while running or recording a test or when trying to connect to the Fabasoft app.test Agent.

This might have different reasons:

  • Connection closed unexpectedly
    This error message tells you that a connection error occurred for some reason, e.g. if you closed the Fabasoft app.test Client Adaptor manually even though Fabasoft app.test was currently connecting.
  • No response within xxx ms
    This error message means that something crashed, e.g. the web browser or the third party application. In this case a screenshot is quite helpful because if a "Connection reset" happens a screenshot of the whole desktop is taken.
  • Connection reset
    This error tells you that the connection has been reseted while running the test.

These are some tips for identifying the problem:

  • Screenshots:
    Always select the "On Error: Screenshot" check box (see chapter “"Run" Tab of the "Run" Dialog”) when running a test in the Fabsoft app.test Player. If a "Connection error" occurs, a screenshot of the whole desktop is taken. This might help you identifying the problem.
  • Traces:
    Always open the tracer when running a test in the Fabasoft app.test Player (on the platform where the Fabasoft app.test Client Adaptor is started). These traces can help you after running a test finding problems.

[5004] Invalid Session

This error occurs when an execution is going to be executed on an invalid session. It may occur after a Fabasoft app.test Adaptor crashed and there is no context/connection to an Adaptor for following executions.

[5101] Adaptor startup: <message>

This error tells that there is a problem when starting the Fabasoft app.test Client Adaptor.

[5101] Adaptor startup: The client type <client type> is not supportes on platform "<platform>"

This error is shown if you want to use a client type that is not supported on the current platform.

In the following example the Fabasoft app.test Client Adaptor could not be started because the user tried to start the Microsoft Internet Explorer on an Ubuntu environment.

This error is also shown if you try switching to a context which is not allowed on the current platform, e.g. if you try to switch to Microsoft Outlook even though the test is executed on an Ubuntu platform. In that case, also an "Adaptor startup" error is thrown which can be seen in the report.

[5102] License check failed: <message>

The message "License check failed: <message>" is shown if problem occurs with the license used in the tested Fabasoft Folio domain.

You can find the reason for the error when performing the license check in the brackets of the error message. This message is returned by the Fabasoft Folio domain.

These are some possible messages and their solutions:

  • Software Product "ComponentApptest@1.1" not found
    This means you have to install the software product "Fabasoft app.test" additionally to your Fabasoft Folio domain.
  • The license has expired
    You must renew your license.

[5103] Client Certificate: <errormessage>

This indicates that there is a problem with the client certificate in Microsoft Internet Explorer.

[5201] SOAP fault: <errormessage>

This message is shown if something went wrong when executing a SOAP call.

The error is displayed that is sent by the Fabasoft Folio domain: "SOAP fault: <message>"

[5201] SOAP fault: Your access rights for "Evaluate expression via XML/SOAP" are not sufficient

If you try to execute a Fabasoft Folio expression, the following error might occur: Your access rights for "Evaluate expression via XML/SOAP" are not sufficient

This message is displayed if you are not allowed executing Fabasoft Folio expressions via Fabasoft app.test. This means you have to set the corresponding rights in the "ACL for Expression Evaluation" (see chapter “Set Statement”).

[5301] Agent: <errormessage>

This error is displayed when a Fabasoft app.test Agent related error occured, e.g. if there is a problem streaming files to the Agent machine or the Agent update operation failed.

[5401] Telemetry: <errormessage>

This error occurs when there is a problem starting or stopping an app.telemetry session.

[5501] Adaptor information: <errormessage>

This error occurs if there is a problem when requesting information (like the OS type or version information) from the Fabasoft app.test Adaptor.