Overview #
Agent Testing and QA is the process of checking that your Agent works as expected before releasing it to real Candidates. This includes testing the flow, verifying data, and confirming that everything displays correctly.
Why This Matters #
Testing prevents:
- Broken flows that stop Candidates from progressing
- Wrong routing that sends Candidates to the incorrect Path
- Missing or incorrect data in messages and confirmations
- Failed integrations (email, SMS, webhook)
A well-tested Agent creates a smooth and professional experience for every Candidate.
How to Test Your Agent #
1. Plan Your Test Scenarios #
Before testing, list the key scenarios you want to check:
- Happy path — The ideal Journey from start to finish
- Alternative paths — What happens when the Candidate selects different options?
- Edge cases — What if the Candidate skips a field, times out, or goes back?
2. Run Through the Journey as a Test Candidate #
- Create a test Candidate (or use the built-in test feature).
- Go through the Journey Step by Step.
- At each Step, check:
- Does the content display correctly?
- Are Merge Fields showing real data (not blank)?
- Do buttons and options work as expected?
- Complete the full Journey to the Outcome.
3. Check Data and Results #
After completing the test:
- Open the test Candidate's record
- Verify that all data was saved correctly
- Check the Journey Timeline for the correct sequence of events
- Confirm the Outcome matches expectations
4. Test Integrations #
If your Agent uses integrations:
- Check that emails were sent (see sent messages in the Candidate record)
- Verify SMS delivery
- Review Webhook Logs for external data delivery
- Test document signing flow end to end
5. Fix and Retest #
If you find issues:
- Fix the configuration in the Agent Editor.
- Run the same test scenario again with a new test Candidate.
- Repeat until the issue is resolved.
What to Test #
| Area | What to Check |
|---|---|
| Flow | Steps appear in the correct order |
| Content | Messages, labels, and instructions are correct |
| Merge Fields | Dynamic data displays correctly (not blank) |
| Options / Routing | Selecting different options leads to the correct next Step |
| Integrations | Emails, SMS, and webhooks are sent successfully |
| Completion | Journey ends with the correct Outcome |
| Timing | Waiting periods and timeouts behave as expected |
Common Mistakes #
- Only testing the ideal path (forgetting alternative routes)
- Reusing the same test Candidate for every test (use a fresh one each time)
- Not checking what happens when the Candidate goes back to a previous Step
- Ignoring timing-related features (e.g., Waiting Period, timeout)
Tips #
- Test every major change before releasing
- Use realistic test data (not "test123")
- Ask a team member to test as well — fresh eyes catch more issues
- Document any issues you find and how you fixed them