Overview
Test scenarios define the exact steps a QA tester follows to validate a requirement. Each scenario belongs to a requirement and contains ordered steps, tags for categorization, and optional testing notes that highlight important details.
Scenarios bridge the gap between documentation and execution. While requirements describe what should be tracked, scenarios describe how to test it. A well-written scenario removes ambiguity and lets any tester on your team validate tracking without needing to ask questions.
When you include a requirement in a QA plan, all of its scenarios come along. Testers work through each scenario step by step, validating the variables, data objects, and tracking pixels attached to the parent requirement.
Creating a Scenario
Open a requirement and navigate to the Scenarios tab. Click Add to open the Edit Scenario modal. Enter a title that summarizes the test flow, such as "Complete a purchase with a coupon code" or "Submit the contact form with all fields."
Add a description if the scenario needs broader context beyond the title and steps. The description is a good place to explain preconditions, such as "Requires an account with items already in the cart" or "Only applies to logged-in users."
After filling in the title and description, proceed to add steps, tags, and testing notes as described in the sections below. Click Save when the scenario is complete.
Adding Steps
Steps are the ordered actions a tester performs. Each step should describe one clear action, such as "Navigate to the homepage," "Add an item to the cart," or "Click the Place Order button." Steps appear as a numbered list in QA plans.
The system automatically prepends "Open Browser In Incognito/Private Mode" as the first step of every scenario in QA plans. You do not need to include this step yourself. Start your steps with the first meaningful action the tester should take.
Keep steps short and specific. A tester should be able to follow them without any prior knowledge of the site. Avoid combining multiple actions into a single step. If a step requires navigating to a page and then clicking a button, split that into two separate steps.
Tags
Assign tags to categorize your scenarios. Tags help you filter and organize scenarios across requirements, making it easier to find related test flows. For example, you might tag scenarios as "checkout," "mobile," or "logged-in."
You can select from existing property tags or create new ones directly from the scenario editor. Tags are shared across all requirements within a property, so consistent naming helps keep things organized.
Tags are optional but recommended for properties with many requirements. They become especially useful when you need to quickly locate all scenarios related to a specific flow or feature.
Additional Testing Notes
The Additional Testing Notes field lets you provide extra context that does not fit neatly into the steps. Enter notes that highlight anything a tester might otherwise overlook. For example, "Wait 5 seconds after the page loads for the tag to fire" or "Use test credit card number 4111111111111111."
Testing notes appear in red text in QA plans and test case views. This visual treatment draws the tester's attention to important details that could affect test results. Use this field for timing considerations, test data, environment-specific instructions, or known quirks.
If a scenario does not need extra notes, leave the field empty. Only add notes when they provide genuinely useful context that the steps alone do not convey.
Cloning and Moving
You can clone a scenario to create a copy. This is useful when similar test flows apply to different requirements. Click Clone from the scenario list to duplicate it.
When cloning, you have the option to move the copy to a different requirement. This lets you quickly set up related scenarios across requirements without starting from scratch. The original scenario remains unchanged.
Cloning copies the title, description, steps, tags, and testing notes. After cloning, edit the copy to adjust any details that differ between the original and the new context.
Sorting
Drag and drop scenarios to reorder them within a requirement. The order you set here determines the order scenarios appear in QA plans. Put the most critical or foundational scenarios first so testers validate the core flows before moving to edge cases.
Reordering is saved automatically. You can adjust the order at any time without affecting the scenario content or any active QA plan rounds.
Keep steps atomic: one action per step. Use testing notes for anything that is not obvious from the steps alone. Clone scenarios when similar flows apply to different requirements rather than recreating them from scratch. Tag consistently across your property to make filtering useful.
Troubleshooting
Scenario not appearing in QA plan
Scenarios are pulled into QA plans through their parent requirement. If a scenario is missing, check that the parent requirement is included in the plan. Scenarios cannot be added to a plan independently.
Steps out of order
Use drag and drop on the Scenarios tab to reorder steps within a scenario. If drag and drop is not responding, try refreshing the page. The order displayed in the editor is the order testers see in QA plans.
Testing notes not showing
Verify that the Additional Testing Notes field was saved and is not empty. Open the scenario in edit mode and confirm the text is present. If notes were entered but do not appear in the QA plan, check that the plan round was created after the notes were saved.