Test a newsletter signup with double opt-in, end to end
A signup form that says “check your inbox” proves nothing until the confirmation email arrives and its link works. One test signs up, confirms and checks the welcome.

Two steps, two chances to break#
With double opt-in, a signup is not complete when the form is submitted. As Mailchimp's own help describes it, the contact receives a confirmation email and clicks a link to verify, and only then is added to the audience as subscribed. If the confirmation email never arrives, or its link lands on a broken page, the subscriber is silently lost.
It breaks in ways nobody notices: the embedded form is replaced by a page builder's own form that is not connected to the list; a list setting changes; the "thank you" page URL changes in a redesign. The site still says "check your inbox".
The test#
Each Testsy run has its own mailbox, so it can sign up with a fresh address every time:
Open https://client.example/ and scroll to the newsletter signup in
the footer.
Enter this run's email address and press Subscribe.
Check the page says to confirm the subscription by email.
Wait for the confirmation email and check it is from Client Co.
Open the confirmation link in it.
Check the page it opens says the subscription is confirmed.
Wait for the welcome email and check its subject mentions Client Co.If any step fails, the check names it: no confirmation email, a link to a broken page, no welcome.
Things to know#
- A real subscriber is created. Each run adds a confirmed contact to the client's list, with an address ending in
@inbox-test-engine.testsy.dev. Tag or delete them, or point the test at a test audience. - Some tools only send the confirmation from their own forms. One guide notes that with Mailchimp, email double opt-in only works with Mailchimp's own signup forms, not with integrations or the API. If the site's form posts through an integration, the test will show what actually happens.
- Run it weekly, not nightly, unless the client's newsletter is the business. It adds a contact each time.
Proof of the email step#
We have run the email part on our practice site: the tester signed up with its own address, read the message and used it (the run, live until 18 February 2027). The full post: Test email verification codes.
This post is part of Find the bug before your client does.
Filed underWebForms and checkoutEmails and messagesClient sites