A developer describes being asked how they test websites and then actually running the checks they’d only described. A contact form saved requests in WordPress, the admin UI showed the submission, and WordPress reported the email as sent, while the server’s mail program accepted the message and immediately marked it deferred - so nothing reached an inbox. The developer wrote a tool that queried every WordPress site on the same server: of 31 sites, 29 claimed delivery while no email left the server. The point is concrete: success return values, log lines, and 200 status codes are not the same as the real-world outcome of a person receiving an email; a written testing claim must include a live check.
A separate real-device check found a UI bug a headless browser missed: a yellow “request an estimate” bar overlapped the hero’s yellow button on iPhone, creating duplicated controls that didn’t appear in automated layout checks. The author fixed the mail flow so a proof email landed in the client’s inbox and deployed new imagery for a site owner, noting that one honest test revealed failures and enabled repairs - with twenty-nine more sites left to bring from false success to verified delivery.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.