Validate backend logic with unit and integration tests for HTTP routes and Postgres.
npx skills add https://github.com/weiloon1234/Forge-Starter --skill testing-weiloon1234
Please help me install this Agent Skill. Skill: testing Source: https://github.com/weiloon1234/Forge-Starter/tree/main/.claude/skills/testing Command: npx skills add https://github.com/weiloon1234/Forge-Starter --skill testing-weiloon1234
Use when writing or extending test coverage for backend code — pure-function unit tests inside src/domain/services/<name>_service.rs, or end-to-end integration tests under tests/<scenario>.rs that boot the real HTTP kernel + real Postgres and hit endpoints with authentic auth tokens. Covers the decision between unit vs integration tests, the shared boilerplate (reset_database / run_cli / boot_api / send_json), authenticated-request patterns, fixture construction, and test-database safety. Does NOT cover frontend component or E2E tests (no vitest / playwright set up yet), benchmarks, property-based tests, or Forge framework tests.
Begin by adding a unit test for a function in the target service, then create an integration test scenario under tests/ that boots the real kernel and hits an endpoint with a valid auth token.
High-intent search queries and answers about installing and using this skill.
Rust backend unit tests belong inside a #[cfg(test)] mod tests block within the domain service module, while integration tests live under the tests/ directory to exercise HTTP endpoints and real database interactions. This separation ensures pure logic and end-to-end flows are validated independently.
Integration tests against real Postgres require shared boilerplate utilities including reset_database to clear state, boot_api to start the HTTP kernel, run_cli for commands, and send_json for authenticated request payloads. These helpers ensure repeatable and safe test-database interactions.
Write unit tests for pure functions inside domain services to validate isolated logic quickly, and use integration tests under tests/ when you need to exercise HTTP routes with authentic auth tokens and real database interactions. Choose integration tests for end-to-end flow validation.
No, this does not cover frontend component tests, E2E tests, benchmarks, property-based tests, or Forge framework tests. It applies exclusively to backend unit tests inside domain services and integration tests exercising HTTP routes with real Postgres databases.
Use fixture builders and shared test helpers to construct deterministic data, and call reset_database before each test run to ensure test-database safety. This prevents state leakage between tests and guarantees repeatable end-to-end integration test execution.
anderskevConfigure Vitest projects with unit and integration tests using mocking and snapshots.
fattits30-devRun Vitest and Playwright tests with native module rebuilds and coverage reports.
Ahmednoorani258Integrate Better Auth with JWT tokens for Next.js 16 and FastAPI authentication.
TimeKastDefine AAA structure, unit/integration selection rules, and mocking guidelines for test suites.
