Testing Guides
Short answer
Authoritative how to test X guides for high-intent scenarios—Stripe, Firebase, chatbots, email, RBAC, and more. Each page includes complexity maps, fixture patterns, probe-first Assert, and page-scoped FAQs—wired to TestChimp QA workflow where it helps maintenance and requirement coverage.
What these guides cover
TestChimp product docs explain features. These guides explain how to test specific scenarios authoritatively—pain points, Arrange/Act/Assert patterns, vendor docs (Stripe, Firebase, Mailtrap), and where TestChimp helps naturally (plans in Git, per-PR test, traceability, explore, evolve).
Pick your section
| Section | Start here | Examples |
|---|---|---|
| Business flows | Stripe payments | Subscriptions, seat licensing, inventory |
| Auth & identity | Firebase auth | MFA, CAPTCHA, RBAC, magic links |
| AI & conversational UX | Conversational UI | Agents, RAG, evals + E2E |
| Integrations | Stripe webhooks | Email, PDF, maps, Supabase, Next.js |
| UI patterns | Localization | Forms, grids, GDPR, non-functional |
| Common gotchas | Selector drift | World-state, auth pollution, snapshots, feature flags |
| E2E foundations | Seed routes & probes · TMMi Level 5 | Fixtures, traceability, data-driven maturity |
| E2E in CI | GitHub Actions parallel | Sharding, traces, reporters |
| Industry | Checkout | HR, healthcare, travel, multi-tenant |
| Built with | Cursor | Lovable, agent workflows |
| Performance testing | Load testing | Volume, k6 vs JMeter, regression across releases |
How TestChimp applies to these guides
| 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 annotation 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 (Workflows) |
| 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 |
| Performance testing | k6 journeys for load and volume; compare p95 / 4xx / 5xx across releases — product docs: Performance Testing |
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.
Shared workflow
- Read the guide for your current risk area
- Copy Arrange/Act/Assert patterns into markdown scenarios (test planning)
- Run
/testchimp initif harness is not scaffolded - Gate PRs with
/testchimp test; expand from plan gaps and production signals with/testchimp evolve
Canonical pattern: expired-coupon narrative.
Related hubs
Frequently asked questions
Which testing guide should I read first?
Match your sprint risk: Stripe or webhooks for payments, Firebase for auth, conversational UI for chat features, transactional email for signup flows. All guides share probe-first Assert and per-run fixtures.
How do these guides differ from product documentation?
Product docs explain TestChimp features; guides explain how to test specific scenarios with vendor best practices, complexity maps, and FAQs aimed at search and AI answers—TestChimp workflow is mentioned where it naturally helps maintenance and requirement coverage.
Where are the performance testing guides?
Under Performance testing: load vs volume, load patterns (ramp, spike, soak, stress), p95/4xx/5xx metrics, k6 vs JMeter vs Locust, and comparing runs across releases. Product how-to lives in Performance Testing.
Do I need TrueCoverage to use these guides?
No. Guides stand on Arrange/Act/Assert and probe patterns alone. TrueCoverage, ExploreChimp, and /testchimp evolve add post-deploy insight when you adopt the full TestChimp loop—not a prerequisite for every scenario.
Are long guides like Stripe and Firebase kept up to date?
Flagship guides document edge cases (3DS iframes, webhook idempotency, Auth emulator CI) with links to official Stripe and Firebase docs—regenerate from scripts/scenarioPages when updating the content registry.