be-test

Generate backend unit and integration tests from test-case documents and API specs.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/gridi-ai/gridi-skills --skill be-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: be-test
Source: https://github.com/gridi-ai/gridi-skills/tree/main/skills/be-test
Command: npx skills add https://github.com/gridi-ai/gridi-skills --skill be-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams convert test-case documents and API specs into ready-to-run backend tests, reducing manual effort and speeding feedback loops for quality.

Core Features & Use Cases

  • Unit and integration test generation from test cases and specifications.
  • Framework-aligned test scaffolding that follows project conventions and ID strategies.
  • API-driven validation enabling test coverage from specification to implementation for backend services.

Quick Start

Run the be-test skill against your test-case documents to generate backend tests aligned with your project's framework.

Frequently Asked Questions about be-test

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

FAQPage Schema
How do I generate backend tests from test-case documents and API specs?

You can generate backend tests by running the skill against your test-case documents and API specs. It produces organized unit and integration test files with clear naming and structure, aligned to your project's framework.

Can I generate both unit and integration test scaffolding for backend services?

Yes, you can generate both unit and integration test scaffolding for backend services. The skill implements tests according to your project's chosen framework and conventions, ensuring proper test coverage from specification to implementation.

How does backend test generation handle project-specific testing conventions?

Backend test generation handles project-specific conventions by validating inputs against crew-config.json. It applies your project's chosen framework and ID strategies to produce organized test files that follow your established structure.

Do I need API specs to automate backend test code generation?

You need both test-case documents and API specifications to automate backend test code generation. The skill uses these inputs to validate test coverage and produce ready-to-run test files for your backend services.

What is the best way to convert test cases into ready-to-run backend tests?

The best way to convert test cases into ready-to-run backend tests is to use an automated skill that reads your test-case documents and API specs. This reduces manual effort and speeds up quality feedback loops.