Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Our signup funnel is: register, receive an email, click the link, land verified. I can test the first step and the last step and nothing in between, so the coverage stops exactly where the interesting failures are. Invitations and 2FA enrolment have the same shape.
Is there an inbox adapter or an email step I have missed?
Accepted answer
Nothing ships. No mail adapter, no inbox steps. There is an open issue proposing a Mailpit adapter and a set of inbox assertions; it has not been built.
The workaround I would push you towards is not "wait for the framework" — it is to stop routing the test through the mailbox at all where you can:
it there and drive the link directly. You keep the assertion that matters (the link works, the account ends up verified) and lose only the assertion that mail was delivered, which is your provider's job more than yours.
accept that it is the slow one.
If you genuinely have no such surface, run Mailpit in your test environment and write project steps against its HTTP API. That is exactly what the proposed adapter would do — you are writing it yourself a bit earlier, and it is maybe fifty lines.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.