qa-engineer

Designs and runs multi-layer test automation for Flutter and Firebase applications.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/yunior123/origna_gta_firebase --skill qa-engineer-yunior123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/yunior123/origna_gta_firebase/tree/main/.claude/skills/qa-engineer
Command: npx skills add https://github.com/yunior123/origna_gta_firebase --skill qa-engineer-yunior123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a Flutter web and mobile marketplace without a QA team means regressions, payment bugs, and security holes slip into production. This Skill provides a complete multi-layer testing strategy covering unit, integration, E2E, visual, accessibility, performance, and adversarial security testing. ## Core Features & Use Cases - Multi-Layer Test Strategy: Coordinates pytest backend tests, Flutter widget tests, Playwright E2E, Patrol/Maestro mobile tests, golden tests, Lighthouse CI, k6 load tests, and OWASP ZAP security scans. - Adversarial Test Patterns: Provides 50+ mandatory attack scenarios covering payment tampering, race conditions, data isolation, input boundaries, and file upload abuse. - Test Gap Prioritization: Identifies critical coverage gaps (mobile native testing, offline mode, concurrent checkouts, cross-browser) ranked by launch risk. - Use Case: Before a production launch, ask the agent to audit test coverage for the checkout flow; it runs the existing pytest and Playwright suites, identifies missing adversarial cases like double-charge and stock race conditions, and writes the new tests. ## Quick Start Ask the agent to audit the checkout flow test coverage and write the missing adversarial payment tests.

Frequently Asked Questions about qa-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a Flutter app end-to-end on mobile?▼

Use Patrol for native iOS and Android E2E tests written in Dart, which handles system dialogs, gestures, and deep links. Maestro is an alternative for no-code YAML-based smoke tests runnable in CI.

What is the best tool for Flutter web E2E testing?▼

Playwright works well for Flutter web E2E when combined with semantics-based selectors instead of CSS selectors. It supports API testing, Firebase emulator integration, and Stripe checkout flows in the same suite.

How do I test Stripe payment flows without real charges?▼

Run tests against Firebase emulators with Stripe test keys, and use idempotency keys to verify duplicate submissions are deduplicated. Test webhook replay by sending the same event.id twice and asserting the second processing is a no-op.

Patrol vs integration_test for Flutter testing?▼

Patrol adds native platform interaction like permission dialogs and notifications on top of flutter_test, while integration_test only controls the Flutter widget tree. Use integration_test for widget flows and Patrol when tests cross into native UI.

How do I handle flaky Playwright tests in CI?▼

Set retries to 1 in the Playwright config, isolate each spec by resetting emulator state, and run with a single worker to avoid race conditions. Track known flaky tests separately rather than letting them block the pipeline.

What adversarial tests are needed before launching a payment app?▼

Cover price tampering, double-charge via repeated idempotency keys, webhook replay, self-purchase, stock race conditions on the last item, and cross-user data access. Each attack should assert the backend rejects it with the correct error code.