test-conventions

Standardizing bun:test imports involves enforcing specific import statements and reusable factory helpers for configuration setup. This ensures all SDK tests adhere to defined patterns for reliable state management and consistent initialization.

Mocking payment adapters and stores in a bun:test environment utilizes provided mocking utilities to simulate interactions. This standardizes adapter testing practices to ensure reliable validation without relying on actual external payment systems.

Testing time-based logic without system time requires using an injectable clock pattern within your test suite. This facilitates deterministic time-based testing by allowing explicit control over time progression during test execution.

Writing concurrency and error assertions for race conditions involves applying defined bun:test patterns for robust testing. This validates error handling and concurrent operations to ensure reliable SDK behavior under simultaneous execution loads.

The test-conventions skill exclusively enforces exact bun:test conventions and does not support other testing frameworks. It standardizes SDK testing practices by requiring all tests to use bun:test for imports, mocking, and assertions.

Using standardized testing conventions for SDK state management ensures tests are clear, repeatable, and cover critical functionality. This enforces consistent methodologies across test suites, improving reliability and maintainability during SDK development.