bte

Plans Rust backend unit and integration tests by inspecting PetCare service and model definitions.

1|Updated Sep 9, 2025
One-click install
npx skills add https://github.com/davidting0918/PetCare --skill bte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bte
Source: https://github.com/davidting0918/PetCare/tree/main/.claude/skills/bte
Command: npx skills add https://github.com/davidting0918/PetCare --skill bte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend testing for the PetCare repository is streamlined by a dedicated skill that guides review, refactor proposals, and automated bootstrap of missing unit tests. It codifies the testing strategy and consolidates how to approach unit, integration, and discussion tasks.

Core Features & Use Cases

  • Review existing unit and integration tests to identify gaps and refactor opportunities.
  • Bootstrap a fresh unit test file for a domain when none exists.
  • Propose test strategies and communicate them through the /bte subcommands (unit, integration, discuss).

Quick Start

Invoke /bte with a subcommand and domain to bootstrap, review, or discuss tests for that domain.

Frequently Asked Questions about bte

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

FAQPage Schema
How do I bootstrap backend unit tests for a domain that has no existing test files?

To bootstrap backend unit tests, invoke the skill with the unit subcommand and target domain to automatically generate a fresh unit test file by inspecting existing service and model definitions.

What is the best way to identify gaps and refactor opportunities in existing backend integration tests?

Review existing backend integration tests by invoking the integration subcommand, which inspects service definitions to identify coverage gaps and propose refactoring opportunities across targeted domains.

How should mocked database interactions be handled when generating backend tests?

Backend tests must use mocked database interactions and avoid network I/O entirely, ensuring unit and integration tests run deterministically without hitting external services or live database connections.

Can I discuss and plan a testing strategy for specific PetCare domains like auth, user, and pet?

Yes, you can use the discuss subcommand to plan testing strategies and communicate best practices for specific domains including auth, user, group, pet, food, meal, and weight.

Does the backend test generation work across all PetCare service domains?

The backend test generation applies across multiple PetCare domains including auth, user, group, pet, food, meal, and weight, enabling unit review, bootstrap, and strategy discussion for each.

What limitations exist when refactoring tests to avoid network I/O in the PetCare repository?

Tests are constrained to mocked DB interactions and must avoid network I/O, meaning refactoring proposals focus on isolating service logic and preventing direct external API or database calls during execution.