Unit Testing

Advanced pytest patterns including fixtures, markers, plugins, and async testing.Use when implementing test infrastructure, organizing test suites, using pytest plugins,or setting up complex test scenarios with fixtures and parametrization.Triggered by: pytest, fixtures, parametrize, conftest, test organization, async testing.

Use when GitHub PR or branch has failing checks and you need to find Konflux pipeline information (cluster, namespace, PipelineRun name). Teaches gh CLI commands to identify Konflux checks (filter out Prow/SonarCloud), extract PipelineRun URLs from builds and integration tests, and parse URLs for kubectl debugging.

OpenFeature vendor-agnostic feature flag SDK with standardized API acrosslanguages. Covers SDK installation, flag evaluation, providers, and hooks.Use when implementing feature flags, A/B testing, canary releases, or whenuser mentions OpenFeature, feature toggles, or progressive rollouts.

Validate test effectiveness with mutation testing using Stryker (TypeScript/JavaScript)and mutmut (Python). Find weak tests that pass despite code mutations.Use when user mentions mutation testing, Stryker, mutmut, test effectiveness,finding weak tests, or improving test quality through mutation analysis.

To apply latest code changes to a running Flutter app, trigger hot reload after connecting to the Dart Tooling Daemon.

This skill provides comprehensive guidance for setting up and configuring test environments for VS Code extension projects. Use when initializing a new test infrastructure, configuring test runners (Mocha, Jest), setting up CI/CD test pipelines, integrating coverage tools (c8, nyc), or troubleshooting test configuration issues.

Write focused tests for core user flows and critical business logic, testing behavior rather than implementation, with clear names and fast execution. Use this skill when writing unit tests, integration tests, or end-to-end tests. When testing critical user workflows and primary application features. When creating tests that focus on what code does rather than how it does it. When mocking external dependencies like databases, APIs, or file systems. When naming tests to clearly describe the scenario and expected outcome. When keeping tests fast and independent. When completing feature implementation and adding strategic tests at logical completion points. When working with test files or test frameworks.

Test patterns with Playwright browser automation. Navigate to deployed patterns, interact with UI elements, verify functionality. Use when testing patterns after deployment or when debugging pattern behavior in browser.

This skill should be used when determining which Buck2 targets are affected by code changes for incremental builds and tests. Use this when users ask to test/build changed code, find affected targets, or run incremental workflows with jj revisions.

Automatic selection of appropriate test tiers based on change scope. Guides unit tests for small changes, full suite for larger changes. Use when running tests, discussing testing strategy, or after code modifications.

Knip finds unused files, dependencies, exports, and types in JavaScript/TypeScript projects.Plugin system for frameworks (React, Next.js, Vite), test runners (Vitest, Jest), and build tools.Use when cleaning up codebases, optimizing bundle size, or enforcing strict dependency hygiene in CI.

Automatically generate and post detailed bug reports to GitHub Issues for the active project repository. This skill should be used when documenting bugs discovered during development, creating professionally formatted GitHub Issues with reproduction steps, technical insights, and recommended E2E tests.

OpenShift z-stream release workflow and orchestration expert. Use when discussing release tasks, build promotion, test analysis, advisory workflows, or any aspect of the Konflux/Errata release pipeline. Provides context on task sequencing, checkpoints, and MCP execution for releases 4.12-4.20.

eXtreme Programming Test-Driven Development (XP-style TDD) Skill. This skill provides both reference documentation AND execution capabilities for the full PLAN -> RED -> GREEN -> REFACTOR workflow.

Validate a connector by running the test suite, diagnosing failures, and applying fixes until all tests pass.

Use when user asks about Konflux resources, Custom Resources, Applications, Components, Snapshots, IntegrationTestScenarios, ReleasePlans, ReleasePlanAdmissions, or namespace placement. Provides quick reference for what Konflux resources are, who creates them, and where they belong (tenant vs managed namespace).

Python testing with pytest, coverage, fixtures, parametrization, and mocking.Covers test organization, conftest.py, markers, async testing, and TDD workflows.Use when user mentions pytest, unit tests, test coverage, fixtures, mocking,or writing Python tests.

Implement test utilities that write test data to the source system and validate end-to-end read cycles.

Check the status of Vizzly visual regression tests. Use when the user asks about test status, test results, what's failing, how tests are doing, or wants a summary of visual tests. Works with both local TDD and cloud modes.

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.