unit▌

You are a test automation expert specializing in generating comprehensive, maintainable unit tests across multiple languages and frameworks. Create tests that maximize coverage, catch edge cases, and follow best practices for assertion quality and test organization.

Testing Spring Cache annotations without external infrastructure using in-memory cache managers. \n \n Covers testing @Cacheable , @CacheEvict , and @CachePut annotations with patterns for verifying cache hits, misses, and invalidation \n Uses ConcurrentMapCacheManager for fast, isolated unit tests instead of Redis or other external caches \n Includes verification strategies via mock call counts, conditional caching with unless and condition parameters, and custom cache key generation with SpEL

Testing Spring ApplicationEvent publishers and listeners with mocked dependencies and event capture patterns. \n \n Mock ApplicationEventPublisher in unit tests and use ArgumentCaptor to verify published events and their data integrity \n Test @EventListener method invocation directly by instantiating listeners and invoking handler methods with captured events \n Handle asynchronous event processing with Thread.sleep() or Awaitility to verify async listener completion \n Verify listener side eff

dbt unit tests validate SQL modeling logic on static inputs before materializing in production. If any unit test for a model fails, dbt will not materialize that model.

Unit testing validates individual functions, methods, and classes in isolation by mocking all external dependencies.

Unit and integration tests use Vitest. Tests run from workspace directories, not the repo root.

Test @Scheduled and @Async methods directly without waiting for actual execution. \n \n Call async and scheduled methods directly in tests instead of relying on Spring's async executor or scheduling intervals \n Use CompletableFuture.get() with explicit timeouts to wait for async results, and Awaitility.await() for polling-based assertions on state changes \n Mock dependencies that async methods call, then verify interactions after completion using Mockito \n Test exception handling by catching

Test Spring @ConfigurationProperties bindings, validation, and type conversions without full context startup. \n \n Use ApplicationContextRunner to test property binding in isolation, covering simple properties, nested structures, collections, and type conversions \n Verify validation constraints with @Validated annotations, ensuring invalid values fail appropriately and valid configurations pass \n Test default values, profile-specific configurations, and property name mapping (kebab-case to ca

JUnit 5 parameterized testing patterns for running single test methods with multiple input combinations. \n \n Supports multiple data sources: @ValueSource for simple values, @CsvSource for tabular data, @MethodSource for complex objects, @EnumSource for enum testing, and custom ArgumentsProvider implementations \n Includes boundary value testing, edge case coverage, and systematic validation of multiple scenarios with reduced test duplication \n Offers custom display names for readable test out

Unit testing patterns for MapStruct mappers and custom converters with comprehensive transformation validation. \n \n Covers field mapping accuracy, null handling, type conversions, nested objects, bidirectional mapping, enum mapping, and partial updates \n Includes Maven and Gradle setup with MapStruct, JUnit 5, and AssertJ dependencies \n Provides patterns for testing simple mappings, nested hierarchies, custom @Mapping annotations, enum @ValueMapping , and @MappingTarget partial updates \n De