backend-test-additions

Name: backend-test-additions
Availability: InStock
Author: velcrafting

Implement backend tests for domain invariants, endpoint behavior, and job retries.

1|Updated Jan 13, 2026

Search Tags:#backend #unit-testing #integration-testing #contract-testing #tests #regressions

Ready to run

npx skills add https://github.com/velcrafting/codex-skills --skill backend-test-additions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-test-additions
Source: https://github.com/velcrafting/codex-skills/tree/main/skills/backend/backend-test-additions
Command: npx skills add https://github.com/velcrafting/codex-skills --skill backend-test-additions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add backend tests that prove domain invariants, endpoint behavior, and job-related retries.

Core Features & Use Cases

Identify the high-value test layers (unit, integration, or contract) and tailor the minimum set of tests to cover happy paths and failure paths.
Apply deterministic test patterns, fixtures, and mocks aligned with repo conventions to ensure low flake risk.
Use-case example: validate that a service endpoint returns correct status mapping and that a retry policy is respected.

Quick Start

Run the repository's test suite to validate the new backend tests and confirm no regressions.

Frequently Asked Questions about backend-test-additions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add backend tests for endpoint behavior and domain invariants?▼

To add backend tests, identify high-value unit, integration, or contract test layers to verify domain invariants and endpoint behavior. Tailor a minimal set covering the happy path plus two failure paths, using deterministic mocks and repo-aligned fixtures.

What is the minimum set of backend tests needed to prevent regressions?▼

The minimum set of backend tests for regressions includes one happy path and two failure paths. This targeted set ensures high-value scenario coverage while keeping the suite deterministic and low-flake using appropriate mocks and repo conventions.

How do I test backend job-related retries deterministically?▼

Test backend job-related retries by applying deterministic test patterns with appropriate mocks aligned to repository conventions. This verifies that retry policies are respected without introducing flake risk from external dependencies.

When should I use contract testing versus integration testing for backend endpoints?▼

Use contract testing to verify endpoint status mapping and interface agreements, and integration testing for broader domain invariants and job retries. Choose the layer that targets your specific high-value scenarios while maintaining deterministic results.

How do I run new backend tests to confirm no regressions?▼

Run new backend tests by executing the repository's existing test suite commands. This validates the added behavior and regression tests against repo-aligned conventions, confirming no existing functionality is broken.