Skip to main content

How do I validate workflow behavior before production release? (Test Case Template)

Use this template to validate workflow behavior in a Demonstration (UAT) site before production release.

Written by Lauren Baird
Updated this week

Answer

Use the workflow testing test case template to plan and document workflow testing in a Demonstration / UAT site before publishing to production. It helps you test the standard path, alternate paths, and any Stop or Intervention behavior in a consistent way.


Steps

Record the workflow details

  • Workflow Name: __________________________

  • Workflow Type / Program: __________________________

  • Test Environment: Demonstration / UAT

  • Tester Name: __________________________

  • Date Tested: __________________________

  • Workflow Version / Draft Name: __________________________


Complete the pre-test checklist (Required)

☐ Workflow is published to a Demonstration / UAT site
☐ Browser page refreshed after publishing
☐ Tester signed out and back in to ANVL Mobile / ANVL Workflows
☐ Correct Demonstration site selected before starting workflow


Plan your test cases

At minimum, complete two test cases. Three is recommended.

Test Case

Purpose

Test Case 1

Standard / expected workflow path

Test Case 2

Alternate or edge-case path

Test Case 3 (Optional)

Stop or Intervention scenario


Complete Test Cases

Test Case 1: Standard Workflow Path

Goal: Confirm the workflow works as expected under normal use.

During Completion, Verify:

☐ Workflow launches correctly
☐ Questions appear in the expected order
☐ Question wording is clear and spelled correctly
☐ Response options make sense
☐ Categories / sections display correctly
☐ Default routes move the workflow forward

Notes / Issues Observed:



Test Case 2: Alternate or Conditional Path

Goal: Confirm rule-based routing works correctly.

During Completion, Verify:

☐ Rule conditions trigger the correct path
☐ Questions appear or hide as expected
☐ Users are not blocked or sent to dead ends
☐ Workflow still completes successfully

Notes / Issues Observed:



Test Case 3: Stop / Intervention Scenario (If Applicable)

Goal: Confirm Stops and Interventions trigger correctly.

During Completion, Verify:

☐ Stop screen appears when expected (if any Stops)
☐ User messaging is clear
☐ Workflow behavior matches design intent


Complete the Post-Submission Review

After submitting the workflow...

In the Mobile App / ANVL Workflows:

☐ Verify the status shows as Complete (blue, closed circle symbol)

Open the Workflow & Verify the following:

☐ All responses are visible
☐ Responses are grouped under the correct categories
☐ Categories appear in a logical order
☐ Answers reflect what was entered during completion

Notes Validation

Add Note button is visible
☐ Notes questions prompt as designed
☐ Note saves successfully
☐ Note appears under the correct category


Validate the result in ANVL Insights

  1. Open the ANVL Insights Live Feed

  2. Open the submitted workflow

Verify:

☐ Workflow appears in Live Feed

☐ Questions and responses are recorded correctly and grouped in the correct Categories (Headers)
☐ Stop or Intervention is recorded correctly
☐ Details align with what occurred during completion

Notes / Issues Observed:



Issues & Fixes

If issues were found:

☐ Workflow updated
☐ Re-published to Demonstration
☐ Browser refreshed
☐ Re-tested affected paths


✅ Final Test Outcome

☐ Workflow behaves as expected
☐ Ready for Production publishing
☐ Additional changes required

Final Reviewer Notes:



Did this answer your question?