Total 30,804 skills, Testing & QA has 1243 skills
Showing 12 of 1243 skills
Creates isolated container environments for testing local uncommitted changes before pushing. Use when testing library changes, multi-repo coordination, or validating "works on my machine" → "works in CI". Provides git bundle snapshots, embedded git server, selective URL rewriting, and package manager cache isolation. Works with any coding agent via standalone CLI, shell scripts, or Docker Compose.
Framework-agnostic HTTP API route testing patterns, authentication strategies, and integration testing best practices. Supports REST APIs with JWT cookie authentication and other common auth patterns.
Production-ready scripts for Android app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and emulator lifecycle management. Optimized for AI agents with minimal token output. Android equivalent of ios-simulator-skill.
Expert in Python testing with pytest and test-driven development
Diagnose and fix failing pytest tests in the pplx-sdk project, following existing test patterns and conventions.
Run an internal dogfooding program/sprint and produce a Dogfooding Pack (charter, scenario map, routines, dogfooding log + triage board spec, weekly report, ship/no-ship gate). Use for “dogfooding”, “eat our own dog food”, internal beta, and product teams using the product daily to find friction before shipping.
Write and run Playwright E2E tests for Redpanda Console using testcontainers. Analyzes test failures, adds missing testids, and improves test stability. Use when user requests E2E tests, Playwright tests, integration tests, test failures, missing testids, or mentions 'test workflow', 'browser testing', 'end-to-end', or 'testcontainers'.
Testing and diagnosis workflow, including unit tests and browser tests, with automatic diagnosis when tests fail. Suitable for test execution and troubleshooting after code changes.
Debug CI E2E failures from pull requests by inspecting GitHub checks, downloading Playwright reports, and mapping failures to local Nx commands. Use when debugging failed E2E tests in PR workflows.
REQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: React component creation/modification/refactoring, UI changes, new playground features, bug fixes affecting studio UI. Generates Playwright E2E tests that validate PRODUCT BEHAVIOR, not just UI states.
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
Pytest testing patterns for Python. Trigger: When writing Python tests - fixtures, mocking, markers.