Test feature branches on Vercel preview deployments using Chrome automation and Gmail OTP
Testing strategy and design - what to test, how to test, and when testing is overkill. From TDD to integration tests to knowing when to skip tests entirelyUse when "test, testing,…
Designs a risk-based test strategy mapped to acceptance criteria without writing test code unless asked. Use after planning and before or during implementation.
Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing…
Use when the main question is whether current verification is sufficient for a change, which test layers are missing, and where the smallest high-value regression protection…
Planification de stratégie de test incluant la pyramide de tests, les quadrants de tests, la couverture et l'analyse de risques.
Assess verification scope, regression protection, and risk-based test coverage for changes under review or implementation.
For data structure validation: test lengths, relationships, constraints that must hold, verify setup is correct.
Test style rules and the flaky-test red-flag catalog — behavior-not-implementation, DAMP setup, narrow assertions, deterministic-input rules (clock, randomness, ordering, hermetic…
Analyze and score test coverage across all testing dimensions -- unit, integration, E2E, load, visual regression, contract, and accessibility.
Use when when you need to verify that a research software package (e.g., MassQL) maintains functional correctness over time, assess the reliability of a tool before integration…
Composite skill — three-phase test quality pipeline. Chains test-health (assess state) → test-cleanup (remove redundant/brittle tests) → mutation-test (validate surviving suite).
Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation.
Analyzes test suites and tags each test with a standardized set of traits (e.g., positive, negative, critical-path, boundary, smoke, regression).
Execute a test scenario against a team, observing coordination pattern behaviors, evaluating acceptance criteria, and generating a structured RESULT.md.
Use before scaling any message, after a launch underperforms, or whenever positioning is still a hypothesis (pre-users).
Use when a verdict rests on a measured quantity rather than a single deterministic assertion — a noisy/probabilistic output, a performance number, an accuracy or conversion rate.
Triage failing macOS tests across Xcode and SwiftPM workflows. Use when asked to run macOS tests, narrow failing scopes, explain assertion or crash failures, or separate — from…
Playwright E2E testing best practices. Use when writing browser tests, visual regression, or accessibility tests.
QSF project conventions for the Playwright E2E suite. Use when working in the QSF playwright-tests directory (authFixtures, ___ping-* handles, data-test-label test IDs, .auth…
Patterns and conventions for writing *.test.ts files in this project. Load when creating or editing unit test files.
Update, generate, and validate tests using git-workspace-review for change context
Test: Verhandlung, Vergleich und Eskalation: prüft konkret die einschlägigen Tatbestandsmerkmale, Fristen, Belege und Rechtsprechung.
[Tier 2 — Non-Functional: Usability · ISO 25010] Visual regression test workflow — captures baseline screenshots and compares on each run using Playwright snapshots.
Set up Playwright screenshot baselines and CI diffing so UI changes fail pixel-by-pixel instead of by eye.
Run a minimal VoidBox VM smoke test locally. Verifies the VM boots and the LLM responds correctly.
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats). — from kalibr-ai/skills
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
Use when backfilling tests on existing code. Analyzes code through public interfaces, detects the project's test framework, and writes behavior-focused regression tests.
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.
Develops and tests Laravel packages using Orchestra Testbench. Activates when writing package tests, configuring testbench.yaml, managing migrations, defining routes/environment…
TestCafe is a Node.js-based end-to-end browser testing framework by DevExpress that requires no WebDriver installation.
Write integration tests using TestContainers for .NET with xUnit. Covers infrastructure testing with real databases, message queues, and caches in Docker containers instead of…
提供基于 Testcontainers 的 Java 集成测试工作流，用于数据库、中间件和外部依赖的接近真实行为验证。 当任务涉及持久化、消息、缓存、对象存储或多依赖编排时使用。
Use when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags.
The fastest way to get started with TestDriver. Just set your API key and start testing. — from testdriverai/testdriverai
The fastest way to get started with TestDriver. Just set your API key and start testing. — from testdriverai/testdriverai
Comprehensive testing strategies for Guts including unit tests, integration tests, property-based testing, and fuzzing — from AbdelStark/guts
Comprehensive testing strategies for Guts including unit tests, integration tests, property-based testing, and fuzzing — from bg-szy/TOP-SKILLS
Expert at Playwright E2E tests, Vitest unit tests, Storybook interaction tests. Use when writing tests, debugging test failures, or improving test coverage.
Пиши тесты в андроид-проекте правильно. Используй этот навык при написании любых типов тестов (unit, integration, UI), тестировании бизнес-логики и компонентов UI.
Advanced testing: E2E with Playwright/Cypress, property-based testing, mutation testing, contract testing, and CI/CD pipelines.
Use when designing tests, implementing test cases, running tests, analyzing test coverage, or fixing test failures.
Write, run, and analyze structured test suites for Agentforce agents. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create,…
Run OceanBase performance benchmarks and functional tests using obd test. Supports Sysbench, TPC-H, TPC-C benchmarks and mysqltest functional tests.
Testing conventions, CI pipeline rules, and smoke test coverage for SkillHub. Ensures agents write tests correctly and understand the CI gate requirements.
Use when: creating or improving test strategy, unit/integration/e2e coverage, load testing, and quality gates for InfraNexus backend/frontend.
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only…
Tests API authentication mechanisms for weaknesses including broken token validation, missing authentication
Tests REST and GraphQL APIs for Broken Object Level Authorization (BOLA/IDOR) vulnerabilities where an authenticated
Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations — from…
Tests d'API REST et GraphQL avec les outils majeurs du marché, incluant le contract testing et l'automatisation.
World-class test automation - unit, integration, e2e testing strategies, and the battle scars from flaky tests that broke CI/CD pipelinesUse when "test, testing, unit test,…
Production-grade testing strategies for robust, maintainable systems. Covers unit/integration/E2E testing, contract testing, accessibility, mutation testing, and CI/CD patterns.
Expert knowledge of testing Node.js and Express applications including Jest configuration, Supertest for API testing, unit vs integration vs e2e testing, mocking external APIs,…
Test across multiple browsers and devices for cross-browser compatibility. Use when ensuring cross-browser or device compatibility with BrowserStack, Sauce Labs, LambdaTest, or…
Automatically generates comprehensive test suites (unit, integration, E2E) based on code and past testing patterns.
Test the ÖZEL cart + checkout flow end-to-end (add-to-cart, cart drawer, custom-print pricing/design, checkout validation + success, localStorage persistence).
Principes et outils de chaos engineering pour tester la résilience des systèmes distribués, incluant fault injection et game days.