Tests

Tests are at the heart of Axcept. Every test is attached to a project. A project represents a web application. Learn how to create, manage and run your tests in more details.

Dashboard

The dashboard is your cockpit for creating and managing Axcept tests. If there are no tests defined an assistant is displayed to support you. full

Once a test is created a list of all available tests get displayed.

full

Context menu

Additional actions can be accessed via the test context menu. Click on the ... to access the individual menu items. As we continue to improve Axcept more action items may be added to deliver an even better workflow and user experience.

full

Search

Use the search field to filter the list of available tests. The query will be evaluated against the available test names.

full

Create a test

To create a new test click on the + icon.

full

Once the test editor successfully launched, an empty test template gets created.

full

Per default, the target screen validation is based on a resolution of 1366x768. If multiple screen resolutions are available, you can change the resolution used for the Preview via the dropdown. The same applies for the environment.

small

Modify the test title and description as required by assigning a representative text. To edit title or description click on one of the elements as marked in red below.

full

In general, a test is made up of single individual test steps. Once steps are defined, you can debug them using the Preview button. Each test step consists of a title and type which defines the action to perform. Edit a test step by clicking on the red marked areas below.

large

It is possible to mix different types in the same test. To offer a high grade of flexibility Validation, Interaction and Wait type categories are available. Based on the supported categories the following step options are available.

Validation

  • Screenshot: Performs a screenshot of the currently rendered web application content.
  • Custom: Enables custom script injection during a test. Depending on the boolean return value the step fails or succeeds.

Interaction

  • User Interaction: To perform user interaction events it is possible to simulate them. Out of the box clicking, hovering and typing are supported. More details can be found here.
  • Run Snippet: Choose a custom defined snippet for a test step. More details about snippets can be found here.
  • Run Code: Inline custom functions for a test step as required.

Wait

  • Timeout: Wait for a defined time before continuing test execution.
  • Wait until hidden: Continue until a specific element gets hidden in the web application.
  • Wait until shown: Continue until a specific element gets displayed in the web application.

Make sure always to save your changes; otherwise, they are lost. If you have unsaved changes, a message will be displayed on the bottom right corner of your browser window.

full