Notification Flows
Verifying the messages a product sends: a per-run recipient, programmatic capture of mail, text or push, one-time links, arrival timing. Sign-up and reset journeys stall here.
on this pageshowhide
explore
- Test Identities9 questions
- Disposable Mailboxes3 questions
- Shared Team Accounts3 questions
- Account Hygiene3 questions
- Channel Capture10 questions
- Programmatic Mail Access3 questions
- One-Time Links & Codes4 questions
- SMS & Push Sinks3 questions
- Downstream Realities14 questions
- Delivery Timing3 questions
- Deliverability Drift4 questions
- Template & Locale Checks4 questions
- Resend Idempotency3 questions
- AI & Data Scientistrole
- AI Engineerrole
- Backend Developerrole
- Data Engineerrole
- Frontend Developerrole
- Full Stack Developerrole
- Game Developerrole
- Java Backend Developerrole
- Java SDETrole
- Kotlin Backend Developerrole
- MLOps Engineerrole
- Machine Learning Engineerrole
- QA Engineerrole
- Software Architectrole
- iOS Developerrole
questions
page 2 of 2A password-reset email can be requested repeatedly; how do you pin down how many of its links stay usable?
basics
~20 sRequest the reset several times, keep every link, then attempt them oldest first without completing the flow and count the acceptances. That count is the product's outstanding-link policy, and the case should assert it as an expected number.
What makes text-message and push checks unsuitable for a suite that runs on every change?
basics
~20 sEach send costs real money and reaches a live endpoint belonging to somebody. A suite firing them on every change burns budget, needs consented recipients, and produces sender volume that anti-abuse limits throttle, degrading the product's own deliveries.
A case fails when an activation email misses its arrival deadline. How do you tell a slow delivery from a lost one?
basics
~20 sAt the deadline both look identical: nothing has arrived either way. Separate them with evidence outside the assertion — the record that a send was accepted, a correlation value carried in the email, and continued observation after the case fails.
showing 31–33 of 33