Build a workflow test checklist with edge cases

Pressure-test newly built automated workflows against bad data, API limits, and real-world edge cases before going live.

Prompt

Prompt
Act as an automation QA lead. Create a comprehensive pre-launch test checklist for the automation workflow described below.

Rules:
- Include practical negative test cases and weird inputs, not just happy-path scenarios.
- Cover common failure points: null values, formatting shifts, rate limits, duplicate triggers, and network timeouts.
- Provide an unambiguous pass criteria for every single test case.
- Make each checkpoint testable within standard automation builders like Zapier, Make, n8n, or script runners.

Output format:### Workflow Summary & Risk Surface
### Pre-Launch Testing Checklist (Markdown table: Test ID, Category, Test Scenario & Input Data, Expected Behavior, Pass Criteria)
### Rollback & Recovery Check

Workflow details to test are below:

Example output

Example for: Typeform intake triggering HubSpot contact creation and Slack notification

Workflow Summary & Risk Surface

This workflow captures inbound leads from Typeform, upserts a contact in HubSpot, and posts an alert into Slack. The highest risk points are partial form completions, non-standard phone or email inputs, duplicate submissions from the same user, and API throttling during traffic spikes.

Pre-Launch Testing Checklist
Test IDCategoryTest Scenario & Input DataExpected BehaviorPass Criteria
TC-01Data ValidationForm submitted with empty last name and emojis in first nameWorkflow strips emojis or stores cleanly without crashing CRM stepHubSpot record created; Slack alert renders emojis correctly
TC-02Format ErrorInvalid email format (e.g. missing @ or domain)Intake validates or routes to dead-letter stepRun does not silently halt mid-flow; failure notification triggered
TC-03ConcurrencyUser clicks submit button 3 times in 2 secondsDeduplication step catches duplicate webhook IDsExactly 1 HubSpot contact updated, 1 Slack post generated
TC-04Rate LimitingBatch test sending 50 form submissions within 60 secondsRate limiting delays executions gracefully or uses native retry queue50/50 executions complete successfully without dropped payloads
TC-05Service OutageSlack API simulated as unreachable (500 error)HubSpot contact persists; Slack step logs error and retriesHubSpot record exists; execution marked as warning, not unlogged failure
Rollback & Recovery Check

Before activation, verify that deleting a failed test record in HubSpot does not break subsequent runs, and confirm your automation history keeps raw payload history for at least 7 days.

Written by AI from this prompt. Your results will vary.

Paste your automation details (triggers, steps, and target apps) directly below the prompt in ChatGPT, Claude, or Gemini. Ask the model to suggest dummy test data values if you need ready-to-use inputs.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Automation & Workflows