Skip to content

2.5 Synthetic Web Tests

Describe the purpose, implementation, and limitations of synthetic web tests

ThousandEyes transaction tests are synthetic web tests that simulate multi-step user journeys through web applications. They go beyond single page load tests by interacting with the target application to test complete workflows. This makes transaction tests ideal for monitoring key business processes in web apps, such as:

  • Logging in and accessing data in SaaS applications
  • Searching for a product, adding it to the cart, and checking out on an ecommerce site
  • Scheduling a meeting and joining it in a web conferencing app

Some key features and concepts of ThousandEyes transaction tests include:

  • The ThousandEyes Recorder IDE for recording user actions and generating test scripts
  • Custom markers to measure the duration of specific steps within the overall transaction
  • Screenshots captured at key points for visual validation and troubleshooting
  • Integration with APIs to incorporate data from other systems into the test

It's important to note that while transaction tests can make API calls as part of the user journey, dedicated API tests are more suitable for solely testing APIs directly.

Transaction tests should run at an appropriate frequency to catch issues quickly without overloading the application. Intervals of 5-15 minutes are common. Very frequent tests may require special tuning.

Hands-on Activities

Activity 1: Get started with the IDE recorder

  1. Go to https://docs.thousandeyes.com/product-documentation/getting-started/getting-started-with-transactions#getting-started-with-the-recorder-ide and follow the instructions to setup the IDE recorder.
  2. Choose a user flow that you can record, for example, the login process to office 365 or any other web application that requires a login process (avoid MFA in the getting started process).
  3. Set the transaction script.
  4. Observe the test results.

For a visual guide on configuring transaction tests, watch the following video:

Configuring Transaction Tests

Activity 2: Create a script using a template

  1. Go to the Github Transaction script repository: https://github.com/thousandeyes/transaction-scripting-examples
  2. Select a template and adapt it to your needs.
  3. Set the transaction script and assign it to an agent.
  4. Observe the test results.

Check out the following video for a walkthrough on using transaction test views:

Using Transaction Test Views

Resources

Sample Questions

2.5 Question 1

An engineer needs to create a test to execute a user's workflow where the user has to log in to OneDrive and download a file. The test has to implement a retry mechanism. The engineer has limited scripting experience. What are the actions that the engineer needs to take?

  • A) Create the script from the Office365 > One Drive - Download File template
  • B) Install the ThousandEyes Recorder IDE and record the user flow
  • C) Check the transaction-scripting-examples repository for sample scripts
  • D) All of the above

Transaction Script Example

Exhibit 2.5-1: Transaction Script Example

2.5 Question 2

You're responsible for monitoring the performance of a company e-commerce website. You're considering using ThousandEyes Synthetic Web Tests. Which of the following functionalities of ThousandEyes Synthetic Web Tests would be MOST beneficial for monitoring the e-commerce checkout process?

  • A) HTTP server monitoring
  • B) Transaction monitoring
  • C) DNS monitoring
  • D) Routing visibility

2.5 Question 3

True or False: ThousandEyes Synthetic Tests eliminate the need for any real user monitoring on your online learning platform.

  • A) True
  • B) False