Use Multi Steps when a Test Case needs a sequence of actions with separate expected outcomes. During execution, testers can compare each step with its expected result and record what happened.
Open the script
Open the Test Case and choose the intended version.
Select the Test Script tab.
Use the script-format selector to choose Multi Steps if needed. Resolve unsaved changes before changing formats.
The screenshots below show an older table layout. Current views can display the same fields in step cards.
Add a step
Use the add-step control below the script, or the step menu to insert a step.
Enter the action in Step.
Enter the values or setup needed for that action in Test Data.
Enter the observable outcome in Expected Result.
Select the displayed Add or Save control and verify that the step is saved.
Step | Test Data | Expected Result |
Sign in with a valid test account. | An active synthetic test customer. | The customer’s account page opens. |
Add one available product to the cart. | Product: Blue T-shirt; quantity: 1. | The cart shows the selected product and quantity. |
Open the cart. | Use the cart from the previous step. | The total matches the item price and quantity. |
Write one clear action per step. State the expected result so another tester can decide whether it passed. Use test data appropriate for your environment and keep credentials out of shared scripts.
Edit or arrange steps
Task | Action |
Edit a step | Open its content for editing, make the changes, and select Save. Cancel discards the unsaved edit. |
Insert between steps | Use Add New Test Step and choose Insert Before or Insert After. Save the inserted step. |
Move a step | Use the move controls or drag handle, then review the full sequence. |
Copy a step | Use Clone Test Step, then edit the appended copy. |
Delete a saved step | Use Delete Test Step and confirm the selected step. |
The × or Cancel editing control is not the same as deleting a saved step. Save changes before adding more work or leaving the page.
See Clone a Test Step for copy options.
Use the script during testing
Start the Test Run in the intended work item, Test Folder, or Test Plan. Read the action and expected result, open the step’s Test Data when needed, and record the actual outcome and evidence.
Test Data is input for the procedure; Actual Result records what happened. See View Test Data During a Test Run.
When an existing run needs a script change, review the latest revision workflow before loading it. Saving a script does not automatically retest its steps.