testing▌

IMPORTANT - Path Resolution: This skill can be installed in different locations (plugin system, manual installation, global, or project-specific). Before executing any commands, determine the skill directory based on where you loaded this SKILL.md file, and use that path in all commands below. Replace $SKILL_DIR with the actual discovered path.

Framework for having useful customer conversations that won't lead you astray. Based on a fundamental truth: everyone is lying to you -- not because they're malicious, but because you're asking the wrong questions. Your mom will tell you your idea is great because she loves you. Investors, friends, and even potential customers will do the same. The Mom Test provides rules for asking questions so good that even your mom can't lie to you.

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

Comprehensive testing strategies for iOS and Android mobile apps across unit, UI, integration, and performance layers. \n \n Covers unit testing with Jest, component testing with React Testing Library, and UI automation using Detox, Appium, XCTest, and Espresso \n Includes performance testing, regression testing, and integration testing with backend services \n Provides best practices for test isolation, mocking, meaningful naming, and >80% code coverage targets \n Emphasizes testing on real dev

Contract testing verifies that APIs honor their contracts between consumers and providers. It ensures that service changes don't break dependent consumers without requiring full integration tests. Contract tests validate request/response formats, data types, and API behavior independently.

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

Comprehensive testing patterns for Spring Boot applications covering unit, slice, integration, and container-based tests. \n \n Covers four test types with performance targets: unit tests (< 50ms), slice tests (< 100ms), integration tests (< 500ms), and full context tests with Testcontainers \n Includes patterns for Mockito-based unit testing, JPA/MVC slice testing with focused Spring contexts, and REST API testing with MockMvc and WebTestClient \n Demonstrates Spring Boot 3.5+ @S

Generate complete VectorBT backtesting scripts with data fetch, signals, stats, and plots. \n \n Supports 10+ pre-built strategies (EMA crossover, RSI, Donchian, Supertrend, MACD, SDA2, momentum, and more) with template-based script generation \n Fetches data from OpenAlgo API or loads directly from DuckDB; auto-detects Historify vs custom formats \n Uses TA-Lib for standard indicators and OpenAlgo ta for specialty indicators (Supertrend, Donchian, Ichimoku); includes signal deduplication via ex

Run tests for React codebase across multiple release channels and configurations. \n \n Supports six release channels: source (default), experimental, www, www with variant false, stable, and classic, each with distinct feature flag configurations \n Accepts test patterns, watch mode for TDD, and variant flags to test different code paths \n Requires explicit test pattern argument to avoid running the entire test suite; uses --silent flag to surface failures and --no-watchman for sandboxing comp

Execute and diagnose Go acceptance tests for Terraform providers with structured troubleshooting. \n \n Run focused acceptance tests using go test -run=TestAccFeatureHappyPath with TF_ACC=1 environment variable \n Diagnose failures progressively: retry with -count=1 , enable verbose output with -v , activate debug logging via TF_LOG=debug , and persist Terraform workspace with TF_ACC_WORKING_DIR_PERSIST=1 \n Validate test reliability by intentionally breaking a TestCheckFunc, re-running the test