unit-test-wiremock-rest-api
Unit tests for external REST APIs using WireMock to mock HTTP endpoints. Use when testing service integrations with external APIs.
Unit tests for external REST APIs using WireMock to mock HTTP endpoints. Use when testing service integrations with external APIs.
Unit tests for caching behavior using Spring Cache annotations (@Cacheable, @CachePut, @CacheEvict). Use when validating cache configuration and cache hit/miss scenarios.
Unit tests for @ExceptionHandler and @ControllerAdvice for global exception handling. Use when validating error response formatting and HTTP status codes.
Unit testing Jakarta Bean Validation (@Valid, @NotNull, @Min, @Max, etc.) with custom validators and constraint violations. Test validation logic without Spring context. Use when ensuring data integrity and validation rules are correct.
Use when facilitating BDD collaboration between developers, testers, and business stakeholders. Use when running discovery workshops and example mapping sessions.
Use when configuring GitLab CI/CD variables, managing secrets, or integrating with external secret providers. Covers secure credential handling.
Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.
Use when formatting JavaScript/TypeScript code with Biome's fast formatter including patterns, options, and code style management.
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
Use when creating custom Credo checks for project-specific code quality rules and standards in Elixir.
Use when pylint configuration including pylintrc, message control, plugins, and scoring system.
Use when ruboCop cops including built-in cops, configuration, auto-correction, and development.
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.
Swift code style conventions for clean, readable code. Use when writing Swift code to ensure consistent formatting, naming, organization, and idiomatic patterns.
Use when prettier configuration including options, config files, ignore patterns, and formatting rules.
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
Use when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
Use when configuring Clippy for Rust projects with TOML config, lint groups, attributes, and workspace setup.
Use when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.
Use when configuring Dialyzer for Erlang/Elixir type checking and static analysis.
Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.
Use when eSLint configuration including config files, extends, plugins, and environment setup.
This skill should be used when working with C++ projects, CMakeLists.txt, Ninja, clang-tidy, clang-format, GoogleTest, Catch2, or Modern C++ (C++11-23) language patterns. Provides comprehensive C++ ecosystem patterns and best practices.