testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
Découvrez les skills documentation testing, comparez leurs dépôts et consultez leurs instructions.
Testing patterns and principles. Unit, integration, mocking strategies.
Testing E2E strategies based on Clean Architecture layers with cypress. Trigger: Invoke when writing tests E2E or testing user flows, verifying full integration in realistic scenarios.
This skill should be used when the user asks to 'implement', 'write code', 'build a feature', 'create a function', 'add functionality', 'code this', 'make this work', or needs to write production code for Java/...
Comprehensive testing guidance for TypeScript projects including unit testing patterns, mocking strategies, and test organization best practices
Design a comprehensive Testing Strategy *before* code is written.
Comprehensive testing command for running, writing, and validating tests
Testing strategies, pytest patterns, fixtures, mocking, coverage
Run Playwright E2E tests through Prefect. Use this skill to run tests, view results in the Prefect dashboard.
Comprehensive audit of Expo/React Native app API integration layer. Use when asked to: (1) Review API interactions, auth handling, or token management, (2) Find hardcoded data or screens bypassing API, (3) Veri...
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use Agent Browser CLI for headless browser automation and E2E testing. Invoke when user needs to automate browser tasks, run E2E tests, capture screenshots, interact with web pages, or perform web scraping task...
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
Inspire team coding standards, best practices, and code review guidelines. Use when writing code, reviewing PRs, or ensuring code quality.
Playwright E2E testing specialist for web applications. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing. Keywords: Playwright, E2E, browser testing, automation, Page...
Comprehensive testing skill for GabeDA application - designs test strategies (UAT, integration, smoke, unit), creates tests for frontend (React/Playwright) and backend (Django/pytest), executes tests, analyzes...
Generate comprehensive quality report with metrics and verification. Produces final CHAPTER_XX_VERIFICATION.md and quality_metrics.json for deployment approval.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Phase 6 of Eiffel Spec Kit. Generates adversarial tests, stress tests, and edge case tests. AI chain suggests attack vectors. Use with /eiffel.harden command.
Coordinates testing strategy and execution across all test types. Use when creating test plans, implementing tests (unit/integration/E2E), or enforcing coverage requirements (80% minimum). Applies testing-requi...
Automated code review analyzing security, performance, maintainability, and test coverage. Activated during code reviews or when conducting analysis.
Kit de ferramentas para interagir e testar aplicativos web locais usando Playwright. Suporta verificação de funcionalidade de frontend, depuração de comportamento de UI, captura de capturas de tela do navegador...
Headless browser debugging for QA failures and visual testing. Use when investigating UI bugs, taking screenshots, or inspecting DOM and network requests.
Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Use PROACTIVELY for test reliability, flaky test debugging, fr...
Reviews code against learning-infra project standards for architecture compliance, code quality, tenant isolation, and test coverage. Reviews for REST API patterns, provisioning workflows, and infrastructure be...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.