test-and-quality-assurance

Designs measurable verification strategies including contract, E2E, visual regression, and flake checks.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill test-and-quality-assurance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-and-quality-assurance
Source: https://github.com/Blaze-sports-Intel/uber-engineer/tree/main/plugins/uber-engineer/skills/test-and-quality-assurance
Command: npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill test-and-quality-assurance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It turns vague “make it work” changes into measurable quality by designing the right mix of unit, contract, E2E, visual regression, and performance/accessibility verification.

Core Features & Use Cases

  • Test pyramid strategy: Helps design a layered test plan (mostly unit, then integration/contract, then a smaller E2E set) for faster feedback with better regression coverage.
  • Contract testing & verification: Builds consumer/provider-style contract checks to keep client and server in sync and reduce integration surprises.
  • Visual regression, flake control, and verification rubric: Adds visual gates on a small surface, enforces flake budgets with quarantine, and requires evidence-based “definition of done” checks before claiming completion.

Quick Start

Ask the assistant: "Create a test strategy for the checkout feature that includes unit coverage, contract tests for the orders API, one Playwright happy-path E2E against an ephemeral environment, and a visual regression gate for the order summary card, with a flake budget and evidence checklist."

Frequently Asked Questions about test-and-quality-assurance

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

FAQPage Schema
How do I design a test strategy that covers unit, contract, and E2E testing?

To design a test strategy, establish a test pyramid mix of mostly unit tests, followed by integration and contract tests, and a smaller set of E2E specs to provide faster feedback with better regression coverage.

What is contract testing and how does it keep client and server in sync?

Contract testing builds consumer-provider style checks that verify interactions between clients and servers, reducing integration surprises by ensuring both sides adhere to a shared agreement without requiring full end-to-end deployments.

How do I set visual regression thresholds and manage flaky tests?

Set visual regression thresholds by applying visual gates to a small surface area, and manage flaky tests by enforcing flake budgets with a quarantine process that isolates unstable tests from the main verification pipeline.

Do I need accessibility and performance verification gates for feature work?

Yes, adding accessibility and performance verification gates ensures changes meet real user outcomes rather than just passing builds, providing evidence-backed definition of done checks before claiming feature completion.

Can I generate E2E specs and directory-based coverage reports for a checkout feature?

Yes, you can generate E2E specs, contract pair definitions, and directory-based coverage reporting by requesting a comprehensive test plan that includes specific requirements like Playwright happy-path E2E against an ephemeral environment.