Skip to main content

Write a Plain Text Test Script

Create and save a free-form Test Script with clear setup, actions, and expected outcomes, then record its execution result.

Use Plain Text for a Test Script written as one free-form set of instructions. It suits a short procedure or exploratory checklist when you do not need a separate result for every structured step.

Choose Plain Text

  1. Open the Test Case and select the intended version.

  2. Open the Test Script tab.

  3. Open the script-format selector and select Plain Text. If you have unsaved changes, resolve the save prompt before changing formats.

Script format selector with Plain Text available

This screenshot shows an older layout. The selector displays the case’s current format, which may differ from the example. Changing the format does not automatically convert every field into a finished new script; review the resulting content.

Write and save the script

  1. Open the Plain Text content for editing.

  2. Describe the setup, test actions, and expected outcome. Keep the sequence easy to follow.

  3. Add relevant formatting or images when they explain the procedure.

  4. Select Save, then reopen the script to confirm the saved content.

For example:

Setup
Use a test customer account with an empty cart.

Actions
1. Sign in to the storefront.
2. Add one available product to the cart.
3. Open the cart.

Expected outcome
The cart shows the selected product, quantity 1, and the correct price.

Use synthetic test data. Do not include account passwords or other secrets in the script.

Execute the case

Start a Test Run from the linked work item, Test Folder, or Test Plan. Follow the script, record the actual outcome and relevant evidence, and set the run’s result.

Plain Text is handled as a whole script. If you need separate Step, Test Data, and Expected Result fields with step-by-step results, use Multi Steps.

Update an existing script

Confirm the Test Case version before editing. If a Test Run already exists, saving the case does not automatically replace its captured script. See Update a Test Run to the Latest Script Revision.

If the content comes from a linked reusable collection, open its collection editor to manage the shared content.

Did this answer your question?