2020 November Release

Error MessagesPermanent link for this heading

Here you will find a list of error messages that might occur in Fabasoft app.test when recording or running tests.

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

The error message tells you that the control, where you wanted to perform an action, does not exist (e.g. if you try clicking the "Next" button even though it is not shown).

The error message might occur in these cases:

  • The location in your execution/set statement might be wrong (typing mistakes etc.).
  • Something might be wrong in the tested system so that the control is not shown.

[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 occurred, 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 occurred 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:

  • Change general timeout
    Before starting a test you can change the general timeouts of Fabasoft app.test. The default execution timeout is 30000 ms (30 seconds), the default timeout for starting a session 60000 ms (1 minute) and the default timeout for starting a context 90000 ms (1 minute 30 seconds). You can change the general timeouts in the apptest-config file.
  • Change timeout for statement
    Furthermore, you can define a timeout just for one statement with a Timeout annotation. 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.

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

[1301] Control is disabled @ <element>

If you try clicking a button that is disabled, the error “Control is disabled” is displayed.

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

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

[1501] Drag and Drop: <error message>

This error occurs when e.g. app.test could not find a target to perform a drag and drop event for importing a document or a general error occurs while performing drag and 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.

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.

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

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

[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 web 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 occurred in the tested Fabasoft installation.

A client error also occurs, if the Fabasoft installation 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 session 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.

[1902] The current test has been aborted

This error is thrown when the test has been 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 session has been aborted due to e.g. too many errors, a fatal error which prevents further execution within the session or a failed assertion which cancels the session.

[3001] Invalid statement: <error message>

The "Invalid statement" error is thrown if there is an error in the statement.

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

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

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

This error in thrown if an attribute contains an invalid value.

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

[3301] Syntax error: Error at expression position x

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

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

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

[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 displayed 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.
  • An expected error did not occur when running a test.

[4002] Assertion failed: <error message>

This error is reported when an assertion statement fails.

[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 web browser 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 reset while running the test.

[5004] Invalid Session

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

[5101] Adaptor startup: <message>

This error tells that there is a problem when starting the web browser.

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

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

[5103] Client Certificate: <errormessage>

This indicates that there is a problem with the client certificate.

[5301] Agent: <errormessage>

This error is displayed when a Fabasoft app.test Agent related error occurred, 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.