QA Plans

Overview

QA Plans let you run structured testing rounds against your documented requirements. Each plan groups requirements and their scenarios into a testable format where testers validate data objects, variables, and tracking pixels one by one.

Plans support multiple rounds of testing. The first round establishes a baseline. Subsequent rounds focus on items that failed or were blocked in earlier rounds, letting your team iterate until everything passes. Each round is a snapshot of the requirements at the time it was created.

When a round is closed, you can automatically generate JIRA bug tickets for any failed items. This connects your QA workflow directly to your development backlog without manual ticket creation.

Creating a QA Plan

Navigate to Blueprint and then QA Plans. Click to create a new plan. You will be asked to select which requirements to include. The plan pulls in all scenarios, variables, data objects, and tracking pixels from the requirements you select.

Choose requirements carefully. A plan should cover a logical scope of testing, such as all e-commerce tracking events or all form submission events. You can always create additional plans for different scopes rather than cramming everything into one.

After selecting requirements and saving, the plan is ready for its first round. No testing happens until you explicitly start a round.

Starting a Round

Click New Round to begin testing. Each round captures a snapshot of the current requirements, so any changes you make to requirements after starting a round do not affect that round. This keeps your test results consistent.

You can run multiple rounds for iterative testing. When you start a second or third round, failed items from the previous round carry forward so testers can focus on what still needs attention. Passed items remain visible but do not require re-testing unless the tester chooses to revisit them.

Each round tracks its own set of results independently. This gives you a clear history of how testing progressed over time.

Testing Workflow

For each scenario in the plan, walk through its steps in order. The first step is always "Open Browser In Incognito/Private Mode," which the system adds automatically. Follow the remaining steps as documented.

For each data object, variable, and tracking pixel under that scenario, set its status. The available statuses are: Pass (working correctly), Failed (not working as expected), Blocked (cannot be tested due to an external dependency), Caution (partially working or needs review), and Not Applicable (does not apply to this test context). Add comments for any item that is not passing to explain what went wrong.

Use the preview link in the Environment Links section rather than any other URL. This ensures you are testing against the correct environment and that your results are consistent with other testers on the same plan.

Closing a Round

When all items in a round have been tested, click Close Round. You will be prompted to enter closing comments summarizing the results or noting any outstanding concerns.

During the close process, you can choose whether to generate JIRA bugs for failed items. When enabled, the system creates a JIRA ticket for each failed item, including scenario context, expected values, and the tester's failure comments. This runs as a scheduled job, so tickets may not appear in JIRA immediately.

Once a round is closed, its results are locked. You cannot change statuses or comments on a closed round. To continue testing, start a new round.

Viewing Results

Open a plan to see all rounds and their results. Each round displays a summary with pass, fail, blocked, caution, and not applicable counts. Click into a round to see the full breakdown by scenario.

Within each scenario, you can see the status and comments for every data object, variable, and tracking pixel. This gives you a complete picture of what passed and what needs attention.

Use the round history to track progress over time. Comparing results across rounds shows whether fixes are resolving issues or whether new failures are appearing.

JIRA Integration

When JIRA integration is configured for your property, closing a round with "Generate JIRA Bugs" enabled creates tickets automatically. Each failed item gets its own JIRA ticket with the scenario name, expected values, actual results, and tester comments included in the description.

The JIRA project is determined by your property configuration. Make sure your property has a valid JIRA project assigned before relying on this feature. You can verify this in the property settings.

Bug creation runs as a scheduled job rather than happening instantly. Allow a few minutes for tickets to appear in your JIRA project after closing a round. If tickets do not appear after a reasonable wait, check the troubleshooting section below.

Troubleshooting

JIRA bugs not created

First, verify that the JIRA integration is configured for your property in the property settings. Second, confirm that you selected "Generate JIRA Bugs" when closing the round. Third, remember that bug creation runs as a scheduled job, not instantly. Allow several minutes before checking JIRA. If tickets still do not appear, contact your account administrator to verify the JIRA connection is active.

Round not closing

All items in a round must have a status set before the round can be closed. Check for any items still in an untested state. Open each scenario and look for items without a Pass, Failed, Blocked, Caution, or Not Applicable status. Set a status for every item and try closing again.

Results not showing

A plan must have at least one round before any results are available. If you see an empty results view, click New Round to start testing. If a round exists but shows no data, verify that the plan has requirements selected and that those requirements contain scenarios with variables, data objects, or tracking pixels.