Skip to content
PigeonProbe

Use cases

Test signup and password-reset email

Take signup and password-reset tests past the “email sent” screen. Check the received link, code and recipient, then finish the journey in your app.

Start free trialIntegration guide

Exercise the full account journey

Your application's success screen is one checkpoint. The next is the email: whether it reached the intended address, contains the expected instructions and leads to the right environment.

PigeonProbe receives your synthetic test messages through your existing sender. Testers can inspect them in the browser, CI can assert against the API, and a connected agent can find messages and extract candidate links or codes through read-only MCP tools.

Signup and invitations

  1. Start with a fresh identity. Provision a test address and submit it through the signup or invitation flow you own.
  2. Inspect what arrived. Check the recipient, subject and body. Confirm the message names the right organization or inviter and uses the expected staging hostname.
  3. Follow the verified link. Validate its URL origin before opening it. Then check your application's resulting state: the account is verified or the invited person joined the intended organization.
  4. Check repeated actions. Resend an invitation or verification email and confirm the behavior your application promises for the previous link.

Use synthetic names and test accounts. Keep essential administrator recovery addresses in your regular email service.

Password resets and one-time codes

Keep one test address active for the account while exercising recovery. Record the start time immediately before each reset request and match that recipient so an old reset message cannot satisfy the next assertion.

  • Confirm the reset goes to the intended test account.
  • Check that the link points to the correct application and environment.
  • Complete the reset and verify the application's expected sign-in behavior.
  • Exercise expiration and reuse rules in your application, including an already-used link or code.

For an OTP flow, assert the expected format and complete the action in your app. Extracted codes are candidates from message content; your test decides which one belongs to that flow.

Keep the evidence with the team

When a test fails, a teammate can open the received message and compare its text, sanitized HTML, raw MIME and delivery checks. That helps distinguish an incorrect template or URL from a failure to receive the message.

Paid plans retain new mail for up to 30 days, with shorter retention available. Capture the synthetic evidence you need before it expires. The CI guide shows how to create a recipient, wait for mail and retire the address.

Put it into your next test run

Try this workflow with your normal sender and a PigeonProbe test address. Open the received message in the app, then bring the same check into CI when you are ready. Compare plans and trial limits.

Start free trialReceive your first test message

Related workflows