Testing workflows is vital to ensure that automation works as expected before going live. By testing, you can catch potential issues and verify that the workflow performs correctly in real-world scenarios.
Why Testing Matters
Testing workflows allows you to:
Verify functionality: Ensure every action is executed as intended.
Identify errors: Detect misconfigurations early on.
Refine workflow logic: Test conditional steps, delays, and branching for optimal performance.
Pro Tip: The most reliable method for testing is to use real-like test contacts and trigger the workflow organically. You can also add contacts manually for testing, but results may vary without proper triggers.
Key Features
Test Workflow Button: Manually test the workflow steps without using the actual trigger.
Execution Logs: Step-by-step insights into the workflow's actions, useful for troubleshooting.
Manual Step Advancement: Move contacts through the workflow manually to test actions like time delays or replies.
Note: Ensure the Allow Re-Entry setting is configured if you’re testing with the same contact multiple times.
Part 1: Setting Up Workflow Testing
Step 1: Access the Testing Feature
Navigate to your workflows within the automation section.
Select the workflow you want to test.
Click the Test Workflow button to begin the manual testing process.
Using this button allows you to skip the workflow trigger and run it directly from the first action, which speeds up testing.
Step 2: Select a Test Contact
Choose a test contact from the contact list.
Click Run Test to initiate the workflow for the chosen contact.
Part 2: Reviewing Execution Logs and Manual Advancement
Step 3: Review Execution Logs
After testing, review the execution logs for details on each step and action taken.
Check for successful actions, skipped steps, and errors.
Click on View Execution History for in-depth analysis.
Pro Tip: Execution logs are critical for identifying missing custom values, skipped conditions, or other errors that might disrupt the workflow.
Step 4: Manual Step Advancement
For workflows with specific conditions like “Wait Until Reply,” you can manually advance contacts through the steps to verify correct behavior.
Part 3: Testing SMS and Email Actions
Testing SMS Actions
Use the Send Test SMS button to verify message content.
Review the execution history to ensure messages are being processed correctly.
Note: Custom values might not populate correctly during test SMS sends, and some links may break. Be cautious of spam filters during testing.
Testing Email Actions
Use the Send Test Mail button to check the email content and ensure the proper delivery of messages.
Part 4: Post-Testing Cleanup
Step 5: Clean Up Test Data
After testing, remove test contacts from the workflow to prevent outdated data from influencing the live workflow.
Note: Clearing test data ensures the workflow runs smoothly with real contacts.
Additional Testing Tips
Use Fresh Contacts: For multiple rounds of testing, use fresh contacts or adjust the Allow Re-Entry setting to allow repeated tests.
Test Organically: Trigger the workflow naturally with a real-like contact to simulate live conditions as accurately as possible.
Monitor Execution Logs: Closely watch the logs, especially after changes, to ensure everything is running as expected.
FAQs
Why should I test my workflow before using it with real contacts?
Testing identifies errors, verifies functionality, and helps fine-tune logic before the workflow goes live.
What’s the best way to test a workflow?
Test it organically by triggering the workflow naturally. This gives the most accurate representation of how it will perform.
What should I do if a workflow action fails during testing?
Review the execution logs for detailed information on errors or misconfigurations.
Will the Test Workflow button skip the initial trigger?
Yes, it bypasses the trigger and starts with the first action, which may affect trigger-dependent actions.