Scenario-based transaction monitoring

Scenario-based transaction monitoring

« back to feature list

The most advanced monitoring function in our service allows you to test all kinds of processes on websites, online stores and in web applications.

It provides detection of irregularities that may occur at various steps of processes and are imperceptible to simple monitoring.

scenario-based transaction monitoring

How it works

Our application, with a specific frequency, pretending to be a real user using a regular web browser, performs actions configured in the scenario. It clicks the indicated elements, fills in the form fields, waits for and finally verifies the appearance of specific elements or content.

If the result of the process doesn't correspond to the expected one—or problems occur on any of the scenario's steps—our system will take a screenshot, register a failure and send notifications, providing the number of the step at which the problem occurred.

Configuration

After selecting the monitoring frequency (10, 30 or 60 minutes) you need to create a test scenario. For each step, you need to specify an Action, Element and, in case of several types of Actions, also Content.

The following Actions are available:
  • click the element
  • fill in the form field (you must enter the content that will be entered in the field)
  • select a checkbox/radio-button
  • uncheck the checkbox
  • wait (for a specified number of seconds)
  • wait for an element to appear
  • submit the form
  • check for the presence of a phrase (verification of the correctness of the process).
The element can be determined using:
  • CSS selector
  • xPath expression
  • ID or NAME value
  • content.
You can test the scenario before saving—and, if something went wrong, preview screenshots live.

It may be complicated to properly indicate the Elements, which is why we are happy to help you to configure scenarios for transaction monitoring.

configuration of scenario-based transaction monitoring

Additional information

Monitoring of processes generates real visits via a web browser—and they are recorded by Google Analytics and other JavaScript traffic tracking tools.

Therefore, it is a good idea to create a filter that excludes visits from the "super monitoring" browser (User Agent value) to avoid disruptions in the site's statistics.



« back to feature list