Results for “test”

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

F# testing patterns with xUnit, FsUnit, Unquote, FsCheck property-based testing, integration tests, and test organization best practices.

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

Trigger: TDD, test first, unit testing, integration tests, mock assertions, test-driven dev. Scope: Writing test assertions before coding features, testing paradigms. Boundary: Excludes UX aesthetics or continuous deployment settings.

Provides C# and .NET testing patterns using xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

JUnit 5 testing framework with Mockito integration. Covers unit tests, mocking, and Spring Boot test integration. USE WHEN: user mentions "junit", "java test", "mockito", asks about "@Test", "@Mock", "@InjectMocks", "unit test java", "spring boot test" DO NOT USE FOR: Integration tests with containers - use `testcontainers`; REST API tests - use `rest-assured`; E2E tests - use Selenium; JavaScript/TypeScript - use `vitest` or `jest`

Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations

Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.

C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

Write and organize F# tests using xUnit, FsUnit, Unquote, FsCheck for property-based testing, and integration test patterns with ASP.NET Core and Testcontainers.

Validates API endpoints, performs contract and integration testing, documents issues, and assesses performance and reliability.

C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, or refactoring.

Write unit and integration tests for Angular v20+ applications using Vitest or Jasmine with TestBed and modern testing patterns. Use for testing components with signals, OnPush change detection, services with inject(), and HTTP interactions. Triggers on test creation, testing signal-based components, mocking dependencies, or setting up test infrastructure. Don't use for E2E testing with Cypress or Playwright, or for testing non-Angular JavaScript/TypeScript code.

Generate, execute, and analyze tests for codebases, covering unit, integration, and end-to-end testing with coverage reporting. Use when the user requests testing or provides relevant inputs for this workflow.

This skill should be used when the user asks for "browser tests", "playwright tests", "end-to-end testing", "test user flows", "E2E coverage", "integration tests for UI", "page object pattern", "/e2e command", or discusses automated browser testing. Covers the E2E test loop workflow, Playwright patterns, page objects, and selector strategies.

Generate api test generator operations. Auto-activating skill for Test Automation. Triggers on: api test generator, api test generator Part of the Test Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like "api test generator", "api generator", "api".

Turbine — small Kotlin testing library for kotlinx.coroutines Flows. Provides ergonomic API to test Flow emissions deterministically: awaitItem, expectMostRecentItem, awaitComplete, awaitError. Works with StateFlow, SharedFlow, Channel-backed flows, combine/map/debounce. KMP-friendly. USE WHEN: user mentions "Turbine", "app.cash.turbine", ".test {}", "awaitItem", "Flow testing", "StateFlow test", "SharedFlow test", "expectMostRecentItem", "cancelAndIgnoreRemainingEvents" DO NOT USE FOR: Mobile E2E - use `testing/maestro` DO NOT USE FOR: Compose snapshot - use `testing/compose-snapshot` DO NOT USE FOR: Generic Kotlin testing - use `testing/kotest` DO NOT USE FOR: Suspend function (non-Flow) testing - use `kotlinx-coroutines-test` directly

Write and run unit tests with Vitest, a Vite-native testing framework offering Jest-compatible API, mocking, coverage, and snapshot testing.

Automate the generation and maintenance of unit, integration, and end-to-end tests, as well as test data generation and debugging. Use when writing tests for new features, maintaining existing tests after API/UI changes, generating synthetic test data, or debugging test failures. Essential for ensuring code quality and preventing regressions.

Write unit and integration tests for PHP applications with PHPUnit and Pest. Use when writing PHPUnit unit tests or integration tests for PHP applications.

Generate comprehensive test suites ensuring requirements are met. Strategies for Unit, Integration, and E2E testing.

API Test Suite Builder

Composite skill — diagnose, repair, and validate a test suite end-to-end. Chains test-health (diagnose) → config-drift-detect (gate compatibility) → test-cleanup (prune + add integration tests) → mutation-test (validate survivors) → adr-write (capture decisions) → docs-sync. Use when "the test suite is bad" or you've hit the test-cleanup-bails-at-the-gate failure mode.

Design and implement robust Python tests with pytest, including unit and integration boundaries, fixtures, parametrization, failure cases, and optional property-based tests. Use when adding tests, repairing a test suite, or deciding how Python behavior should be verified.

Automate Test App operations through Composio's Test App toolkit via Rube MCP, with tool discovery and connection management.

Testing patterns and principles. Unit, integration, mocking strategies.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.