2017 October Release

Fabasoft app.test Player: Progress of a Running TestPermanent link for this heading

After the Fabasoft app.test Player has been started, the progress of the running test, sequence or use case is shown in the "Test State" view. In this view you can break, continue or terminate a test and you always have an overview of the test (which execution is currently executed, how many errors have occurred till now, how many statements are still left etc.).

Buttons of the "Test State" viewPermanent link for this heading

All buttons that are needed to control the Fabasoft app.test Player are located in the top right corner of the "Test State" view.

Remove all terminated jobs

Click the "Remove all terminated jobs" button to delete all terminated tests, sequences and use cases from the "Test State" view (the execution of the test file has finished or has been canceled by the user).

Skip Statement

This button is enabled if the Fabasoft app.test Player has stopped. By clicking this button you can skip the current statement (that would be executed when resuming the test run). This is useful if an error occurred and you want to continue the test run.

Resume

By clicking "Resume" the execution of a test, sequence or use case, which has been suspended, can be continued again.

Suspend

The "Suspend" button suspends the execution of the currently selected test, sequence or use case in the "Test State" view. After a file execution has been stopped by using the "Suspend" button it can be continued by clicking "Resume".

Terminate

The "Terminate" button offers the possibility to stop the execution of a test, sequence or use case completely.

On Breakpoint

Clicking the "On Breakpoint" button opens a menu. In this menu you can choose what should happen if a breakpoint occurs (breakpoints can be set in the Fabasoft app.test Recorder). If "Continue" is selected, breakpoints are ignored. By selecting "Break" the Fabasoft app.test Player stops each time a breakpoint is reached. The execution of the file must then be continued manually by the user (by clicking "Resume").

On Error

Clicking the "On Error" button displays a menu. In this menu you can choose what should happen if an error occurs. If "Continue" is selected, the execution of the test, sequence or use case continues with the next statement. Errors are listed in the report that is created when the file execution has finished. By selecting "Break" the Fabasoft app.test Player stops each time an error occurs and must be continued manually by the user. The third possibility is to select "Cancel". In that case the test, sequence or use case stops completely, i.e. it is terminated.

Elements in the "Test State" ViewPermanent link for this heading

In the "Test State" view you can also see the elements of the test which means at what position in the test the Fabasoft app.test Player is currently running. All elements that are located in the test are also displayed in the "Test State" view:

Test

The name of the test is displayed beyond the current state of the test run:

Sequence

The name of the sequence currently executed is displayed beyond the test name:

Use Case

The name of the current use case is displayed beyond sequence name:

Execution

If an execution (see chapter “Execution Statement”) is currently carried out, it is also shown in the "Test State" view (including all options):

Set Statement

If a set statement (see chapter “Set Statement”) is carried out, it is displayed (the parameter name as well as the value it is set to - parameter references are resolved):

Validation

If a validation (see chapter ) is currently executed, its condition is displayed (all parameters that occur in the condition are resolved before they are displayed):

Context Switch

If the context is switched (see chapter “Insert Context Switch”) while the test is executed, it is also displayed in the "Test State" view (the client type and the location as well as the option - is an option exists):

Error

If an error occurs while running a test file, it is also displayed (If On Error: Break is switched on):

State of Running Tests in the "Test State" ViewPermanent link for this heading

This information can be found in the first line of the "Test State" view:

Syntax

<test name>, Scope:<scope> (<state>) [total: <number>, worked: <number>, skipped: <number>] [ok: <number>, warnings: <number>, errors: <number>]

At the beginning of the line you can find the name of the currently executed test and the scope that is used for the current test run.

The current execution state is shown inside the first brackets. The following states are possible:

  • Running:
    The test is currently being executed.

  • Suspended:
    The test has been paused (by clicking the "Suspend" button) but can be continued by the user.

  • Breakpoint:
    A breakpoint has been reached and the test has stopped (only if the option is activated that the Fabasoft app.test Player should stop if a breakpoint is reached - "On Breakpoint" button).

  • Error:
    The execution of the test has stopped because an error occurred.

Note: If an error occurs, you can open the corresponding file by double clicking the error in the "Test State" view. The test file opens in the "Editor Area" view and the line where the error occurred is selected. Please note that the selection might not be correct if you have edited the file while running it in the Fabasoft app.test Player (because the statement is selected by its line number).

  • Finished:
    The execution of the test has finished. The icon is red if errors have occurred and green if the execution has been successful.

  • Canceled:
    The execution of the test has been canceled (e.g. by clicking the "Terminate" button).

In the square brackets you can find information about the statements in the test, how many have already been executed, how many were successful etc.

  • total: <number>
    Here you can find the total number of statements within the file that is currently being executed.
  • worked: <number>
    This indicates the number of statements that have already been carried out successfully.
  • skipped: <number>
    This number tells the amount of statements that have not been carried out. On the one hand, statements occur as "skipped" if they have not been executed because of an if condition. On the other hand, statements are skipped that have not been reached for carrying them out (e.g. if a sequence was terminated because too many errors have occurred).
  • ok: <number>
    This number tells the amount of statements that have been executed correctly.
  • warnings: <number>
    This number tells the amount of statements where a warning occurred when executing them.
  • errors: <number>
    This number tells the amount of statements where an error occurred.