QA Copilot
Décrivez-le. Obtenez un plan de test prêt à relire.
QA Spider Helper transforme une demande en langage courant en un livrable QA structuré — un plan de test, des cas de test pas à pas ou une story de smoke test. Il suit une vraie discipline d’automatisation : localisateurs centralisés, assertions web-first, vérifications d’API shift-left, balisage sûr pour la production. Vous relisez ; rien ne s’exécute sans approbation.
Essayer un exemple de demande
Test plan — Checkout & billing
Coverage plan for the checkout and billing flow: what to test, where it breaks, which environments and data are needed, and what stays out of scope. Review, then approve the cases worth automating.
Scope
- Cart → checkout → payment → order confirmation (happy path)
- Discount / promo codes: valid, expired, already-used, malformed
- Address & tax calculation across billing regions
- Payment: sandbox success, declined card, 3-D Secure challenge
- Order confirmation email + receipt contents (contract, not delivery)
Risk areas
- Price/total mismatch after applying a discount — highest business risk
- Race between address change and tax recompute
- Double-charge on retry after a timed-out payment call
- Currency rounding on multi-item carts
Environments & data
- staging with the payment gateway in sandbox mode (never prod cards)
- Seeded test accounts with empty + populated carts
- A set of promo codes fixtured per state (valid / expired / used)
Out of scope
- The third-party gateway’s own UI (assert our integration, not their page)
- Real email delivery (assert the send contract, not the inbox)
- Shift-left: verify totals via the pricing API contract before the E2E pass.
- Tag the confirmation read-back @readonly so it is safe to run on prod.
Ceci est un exemple préenregistré. Connecté, vous écrivez vos propres prompts — le Helper rédige plans, cas et stories de smoke test pour votre produit, et vous approuvez ce qui est automatisé.
Lancer vos propres prompts →