agentleFS
mejbaurbaharmejbaurbahar/software-tester-skills/skills/email-notification-testing/SKILL.md

email-notification-testing

Skill1 starsChanged 53 days agoMITView on GitHub

Use when testing transactional/marketing email, SMS, push and in-app notifications — capture inboxes (Mailpit, MailHog, Mailosaur), rendering across clients, links/tokens, SPF/DKIM/DMARC deliverability, unsubscribe/consent, timing, retries, and localization.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Security: no secrets/passwords in email.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Email, SMS & Notification Testing

Notifications are user-visible, legally regulated, and easy to break silently. Never test against real customers' addresses.

Capture, don't send

NeedTool
Local SMTP sink + UI/APIMailpit (docker run -p 8025:8025 -p 1025:1025 axllent/mailpit), MailHog
Hosted, CI-friendly inboxesMailosaur, Mailtrap, Testmail, Ethereal
SMSTwilio test credentials/magic numbers, provider sandbox
PushFirebase/APNs sandbox; emulator/simulator receipts
curl -s localhost:8025/api/v1/messages | jq '.messages[0] | {Subject, To, Created}'
curl -s localhost:8025/api/v1/search?query="subject:Reset" | jq '.messages_count'
// Playwright: request reset, read link from Mailpit, complete flow
await page.getByRole('button', {name:'Send reset link'}).click();
const msg = await (await request.get('http://localhost:8025/api/v1/message/latest')).json();
const link = msg.Text.match(/https?:\/\/\S+\/reset\S+/)[0];
await page.goto(link);

What to verify

  • Trigger: sent once per event (no duplicates, no missing); correct recipient (To/Cc/Bcc); sender name/address; reply-to.
  • Content: subject/preheader, personalization tokens (no {{name}} leaks; fallback when missing), currency/date/locale formatting, plain-text alternative, RTL, long names, emoji.
  • Links & tokens: correct environment domain; tracking params; magic links single-use, expire, bound to user; unsubscribe works without login and is honored within 10 days (CAN-SPAM) — immediately is better.
  • Rendering: Litmus/Email on Acid or Playwright screenshots; dark mode; Outlook (Word engine) tables; image blocking + alt text; mobile width ≤ 600px; size < 102 KB (Gmail clipping).
  • Deliverability: SPF, DKIM, DMARC pass (dig TXT, mail-tester.com, Google Postmaster); List-Unsubscribe + One-Click header; bounce/complaint webhooks suppress addresses; warm-up; no spammy content.
  • Timing & retries: send delay SLA; queue outage → retried, not lost; time-zone aware scheduling; quiet hours; rate limits/digest batching.
  • Preferences & consent: opt-in/out per channel/category, double opt-in, GDPR/PECR consent records; transactional mail still sent to unsubscribed users only if truly transactional.
  • Security: no secrets/passwords in email; header injection (\r\n in name/subject); HTML injection; account-existence not leaked by "we sent an email" messaging.
  • Multi-channel: SMS length/segments (GSM-7 vs UCS-2), opt-out keywords (STOP/HELP), short-code compliance; push permissions denied path, deep-link routing, badge counts.

Related

functional-testing, localization-testing, security-testing, compliance-testing, test-data-engineering

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.