testing-unit

Deterministic unit tests for backend services and frontend components require explicit mocking, context injection, and lifecycle setup to isolate execution from real network or database access. This Skill generates those patterns automatically for Drumr applications.

Isolating database access and mocking dependencies in unit tests requires explicit mocking and context injection within an app-level subclass of a shared test kit. This Skill writes those testing conventions to ensure deterministic execution without real database connections.

Standardizing testing conventions across backend and frontend code is possible by extending a shared unit test kit with reusable fixtures, naming, and context helpers. This Skill generates tests that adhere to these shared conventions for both app layers.

Lifecycle setup and teardown are required for isolated unit tests to ensure deterministic execution and clean context between test runs. This Skill writes test code that includes these lifecycle hooks alongside explicit mocking and database isolation.

Frontend testing fails without provider rendering and event simulation because components require specific context providers to function correctly in isolation. This Skill generates frontend test patterns that include provider rendering and event simulation for deterministic outcomes.

Refactoring an existing unit test to be deterministic involves removing real network or database access, adding explicit mocking, and injecting context. This Skill refactors tests to follow isolated patterns using app-level subclasses of a shared testing kit.