Shared Steps

Shared Steps are reusable collections for verification tests. Define a common sequence, such as logging in or reaching the main menu, and reference it from several tests. Future runs of those tests use the collection’s latest saved steps.

Open Tests → Shared Steps to manage collections. The usage in tests column shows how widely a collection is used.

Creating and Editing Shared Steps

1. Click create new and enter a collection name, such as Login.
2. Fill in each step’s goal/instructions and individual expected results. Use show hints for navigation or recovery guidance.
3. Click new step to add steps, and drag them into execution order.
4. Click Create Shared Steps to save, or Update Shared Steps when editing.

For example, a Login collection can open a web app, sign in with configured credentials, and verify that the account dashboard appears. A recovery hint might say: “If the browser’s password-save prompt covers the app, dismiss it before checking the dashboard.” End the collection in a known state so the next step can continue. See Verification Tests for writing guidance.

Promote an Existing Collection

In a verification test, group steps with new collections in the action bar. On the collection, choose promote to shared steps, give it a reusable name, and save the test. The saved collection becomes available to other verification tests.

Import into a Verification Test

1. Open the verification test and select the player receiving the steps.
2. Click import in the bottom action bar, choose one or more collections, and confirm Import.
3. Drag the collection into position and save the test.

You can reference the same collection more than once, for example to return to a common menu between feature checks.

Maintain a Shared Collection

Imported steps stay linked to their shared collection. Use view in shared steps editor on the collection to edit the source, then save it there. The update applies to future runs of every test referencing it.

Use unlink collection from test to remove that reference, then save the test. The shared collection stays available for other tests.