Testing Guides for Integrations
Short answer
Stripe webhooks, email, SMS, maps, PDFs, Supabase—third-party integration E2E. Each guide includes complexity maps, fixture patterns, probe-first Assert, and page-scoped FAQs—wired to TestChimp QA workflow where it helps maintenance and requirement coverage.
Guides in this section
| Guide | What you'll learn |
|---|---|
| Stripe Webhooks in CI | Stripe webhook E2E—signature verification, idempotency, missed events, out-of-order delivery—with Stripe CLI and probe Assert |
| Transactional Email Flows | Email flows need real inbox capture—mocking SMTP misses template and link bugs |
| SMS and OTP Verification | SMS costs and rate limits make stubs essential in CI |
| Webhooks and Async Event Processing | Async systems fail on ordering assumptions and missing idempotency |
| Map Interactions and Geolocation | Maps are flaky in CI—mock geolocation and assert business outcomes via probes |
| PDF Generation and Downloads | PDFs are high-value artifacts—validate content not just download click |
| File Upload Flows (CSV, Images, Docs) | Upload flows fail on size, type, and async scan states |
| CSV Import and Export | Import errors must be row-level; exports must match grid filters |
| Web Push Notification Preferences | Push requires permission handling and preference persistence |
| Embedded Widgets and iFrames | Embeds load async—wait for frame readiness before interaction |
| Supabase Apps with Playwright | Supabase E2E—Auth, RLS, and Realtime with service-role seeds, per-run users, and probe Assert for Lovable and Next |
| Next.js App Router and Server Actions in E2E | Next |
| Algolia and Elasticsearch Search in E2E | Search index E2E—seed catalog, wait for indexing, assert result sets via probe or stable DOM—with debounce and facet combos |
How TestChimp applies to these guides
These guides are scenario playbooks—Arrange/Act/Assert patterns, fixture discipline, probe Assert—not product feature lists. When you wire them into your repo, TestChimp adds:
| Layer | What it does |
|---|---|
| Test planning as code | Markdown scenarios in Git consolidate business rules agents read on every PR (test planning) |
| SmartTests + AI steps | Playwright you own; ai.act / ai.verify for volatile UI without abandoning probes (SmartTests) |
| Requirement traceability | // @Scenario: links connect specs to plan rows—critical in complex products with many dimension combos (traceability) |
| Per-PR QA workflow | /testchimp test in Claude or Cursor with the TestChimp skill—not a web recorder (QA on Autopilot) |
| ExploreChimp | Non-functional bug capture on SmartTest paths—latency, UX confusion, accessibility gaps most suites miss (explorations) |
| Post-deploy evolve | /testchimp evolve closes plan and production gaps; TrueCoverage is one signal among explore findings and requirement holes |
Why record-replay and no-code tools fall short
Browser recorders and web-based no-code suites optimize click capture. They struggle with per-run seed data, probe Assert on authoritative state, requirement matrices in Git, and non-functional regressions on real user paths. TestChimp contrasts that approach: orchestrated QA where Claude (upskilled with the TestChimp skill) maintains SmartTests against markdown plans—see record-replay vs TestChimp.
Other guide sections
- Business flows · Auth · AI UX
- Integrations · UI patterns
- Industry verticals · Built with
- Testing guides hub
Frequently asked questions
Webhooks vs synchronous API—which guide?
Stripe webhooks when fulfillment updates async; Stripe payments for Elements checkout; webhooks-async for generic event pipelines.
Testing Supabase with Lovable exports?
See Supabase guide—service-role seeds server-side, per-run Auth users, probe Assert through RLS.
How do integration guides handle third-party sandboxes?
Official sandboxes (Stripe CLI, Mailtrap, DocuSign demo) plus probe Assert—never UI-only on async handlers.