Plain-Text Editor Embedded Tests

Learn how to include tests within tests to execute standard instructions such as logging in.

Overview

Any test can leverage an embedded test as a building block. When creating a Plain-Text Editor (PTE) test suite, consider instructions that repeat across multiple tests. These may be complete processes, such as logging in to an app. Or they can represent a portion of a process, such as filling out a form.

By embedding standard instructions, test writing becomes faster; you can update an entire test suite more efficiently. Consider this example. Recently, your team updated the login process with 2-factor authentication (2FA). If each test in the suite has its own set of login instructions, you must update every test. But if the login instructions are contained in an embedded test, you only edit once.

Common Use Cases

  • Login instructions
  • State setup steps
    Examples include setting up an account, adding items to your cart, and going through a checkout process.
  • Email confirmation

Creating a Plain-Text Editor Embedded Test

When creating an embedded test, make sure to include the steps necessary to accomplish a single task, such as logging in to an application. An embedded test is a building block to be used in other tests.

Create the test as you normally would. For more information, see How to Create a Plain-Text Editor Test. Ensure the steps provide a logical start and stop.

Identifying Embedded Tests

Embedded tests are marked with an embedded icon on the All Tests page for easy identification. If a test is no longer embedded in other tests, the icon disappears. Use the Embedded Status filter on the All Tests page to view all your embedded tests.

Embedding a Test

  1. Open the test.
  2. Click the “Embed a Test” link or the dropdown next to “Add Step.”
  3. Start typing the test name or test ID to find the embedded test.
Embedding a Plain-Text Editor test.Embedding a Plain-Text Editor test.

Embedding a Plain-Text Editor test.

Embedding a Test in Another Embedded Test

You can embed an embedded (child) test in another embedded test. This is referred to as nested embedded tests.

  1. Open the embedded test.
  2. Click the “Embed a Test” link or the dropdown next to “Add Step.”
  3. Start typing the test name or test ID to find the embedded test.

Can’t Find a Test?

Here are some reasons you might not be able to find a test:

  • The test no longer exists.
  • The test would cause a circular reference to occur.

Updating Embedded Tests

You update an embedded test like any other test. To edit, choose the embedded test from the All Tests page. Alternatively, you can select the embedded test from its parent.

  1. Hover over the embedded test.
  2. Click the Go to Test button.
  3. The child displays in a new tab.
  4. Edit the child test.

Note: After saving your changes, the embedded test is updated in every parent that contains it.

Editing an embedded test.Editing an embedded test.

Editing an embedded test.

The Embedded Test Starting URL

A test’s starting URL is used to preload the platform for testing. You can have testers navigate to the embedded test’s URL. If the embedded test is the first step, click the “Use embedded URL” checkbox. If the embedded test occurs later in the test, use the “Redirect tester” checkbox.

Selecting “Use embedded URL” or “Redirect tester.”Selecting “Use embedded URL” or “Redirect tester.”

Selecting “Use embedded URL” or “Redirect tester.”


If you have any questions, reach out to us at [email protected] or via the chat bubble below.


Did this page help you?