3.8K skills · sorted by relevance
Build Laravel features test first with PHPUnit or Pest. Create tests for models, HTTP endpoints, authentication, and permissions, simulate external services, and measure coverage to see which code your tests exercise.
Write Django and Django REST Framework tests with pytest-django, starting with tests before implementation. Covers test data generation, simulated external services, model and API checks, and coverage reports showing which code the tests exercise.
Create and repair C++ tests, configure GoogleTest and CTest, and investigate failures or inconsistent results. The workflow also covers measuring which code tests exercise and using runtime checks to detect memory errors and race conditions.
Audit an existing test suite to find low-value or duplicate tests and code kept solely for those tests. Receive findings for review, with changes limited to batches you explicitly approve.
Test agent features across local and remote execution environments using integration tests, which check components working together. Covers Docker and Wine setups, test helpers, and configuration-specific skips for the app-server and exec-server split.
Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.
Build end-to-end tests with Playwright and Cypress to check complete user workflows, such as login and checkout. Improve test reliability through stable element selection, independent test data, appropriate waits, and debugging with traces and screenshots.
Migrate existing PowerShell Pester tests through major versions from v3 to v6. The skill guides assertion updates, setup restructuring, mock changes, and execution configuration, using before-and-after test results to investigate failures while preserving what each test checks.
Guide an RxJS 7 project to RxJS Next by testing existing behavior, reviewing how subscriptions start and end, and validating small batches of changes. Record approved behavior choices, verification results, and unresolved blockers in migration reports.
Create, update, and debug Docker-based end-to-end tests for the Composio CLI. Covers running the executable, keeping test data separate, checking command output, and maintaining package manifests within the CLI test suite.
Create unit test scaffolds, sample data, and mocks from code or specifications. Analyze coverage reports to prioritize missing tests, and guide test-driven development through failing tests, minimal implementation, and refactoring.
Write and review Handsontable tests that check intended behavior. The skill guides bug reproduction, meaningful assertions, failure diagnosis, and fresh test runs, while covering mock boundaries and migration of broken legacy tests to Playwright.
Writes, reviews, and debugs property-based tests, which generate inputs to check general rules. Helps test conversions, parsers, normalization, and state invariants, assess whether existing assertions are meaningful, and distinguish faulty rules from implementation bugs.
Run repository tests using commands suited to Python, Node, or Rust projects. Detect the project setup from its files, run the full suite or a selected target, and show passing results or failure details.
Find source files with no matching test references by parsing code without building or running tests. Produces a source-to-test map and suggested test locations, helping plan test additions across supported programming languages.
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.
The English summary is being prepared. Showing the original description.
Generate and structure MATLAB unit tests using matlab.unittest and matlab.uitest features, including class-based tests, parameterized testing, fixtures, mocking, and app testing with gestures. Use when writing, generating, or adding tests, creating test classes, adding test methods, parameterizing tests, setting up fixtures, mocking dependencies, or testing App Designer apps. Do NOT use for running tests, collecting coverage, or CI/CD configuration.
The English summary is being prepared. Showing the original description.
Use when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for requests such as Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest; Write @MicronautTest integration tests with Testcontainers; Configure replacement beans for Micronaut integration tests; Review Micronaut integration test lifecycle and resources. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires a maintainer-authored scenario summary; do not ingest raw outsider-authored `.feature` text. This should trigger for requests such as Implement Quarkus acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Quarkus; Create WireMock JSON mapping files for external HTTP stubs in Quarkus acceptance tests; Configure Maven *AT naming convention and Failsafe plugin for Quarkus acceptance tests; Map sanitized Gherkin scenario facts to Quarkus acceptance tests. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code; Write @SpringBootTest integration tests with Testcontainers; Configure dynamic properties for Spring integration tests; Review Spring Boot integration test profiles. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming @acceptance scenarios before coding, happy path with RestAssured, DB/Kafka test fixtures, WireMock for external REST only, and *AT classes run by Failsafe. This should trigger for requests such as Review Java code for acceptance tests; Apply best practices for acceptance tests in Java code; Implement acceptance tests from Gherkin scenarios in Java; Map feature files to Java step definitions; Review Cucumber acceptance tests for Java services. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use for .NET test design and validation with xUnit v3, Moq, focused regression tests, command tests, service/manager tests, code generation tests, Roslyn helper tests, MiniDb isolation, HTTP stubs, temp directories, and deciding whether to run targeted tests or builds.
The English summary is being prepared. Showing the original description.
Write focused tdmcp tests for one assigned coverage gap. Use for Vitest/msw unit tests, integration tests, bridge tests, CLI/config/resource tests, and regression tests that should raise coverage without weakening behavior.
The English summary is being prepared. Showing the original description.
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
The English summary is being prepared. Showing the original description.