cli-backend-testing

Automate end-to-end backend API testing via the LobeHub CLI against a local dev server.

Updated May 11, 2026
One-click install
npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill cli-backend-testing-zmh13928433602-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-backend-testing
Source: https://github.com/zmh13928433602-sys/lobe-chat/tree/main/.agents/skills/cli-backend-testing
Command: npx skills add https://github.com/zmh13928433602-sys/lobe-chat --skill cli-backend-testing-zmh13928433602-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CLI + Backend integration testing workflow. Use when verifying backend API changes (TRPC routers, services, models) via the LobeHub CLI against a local dev server.

Core Features & Use Cases

  • End-to-end testing of backend changes via the LobeHub CLI against a local dev server.
  • Supports verification of TRPC routers, services, and models in an integrated workflow.
  • Use case: Validate server-side changes after updates by running CLI-based tests to ensure API stability and correct responses.

Quick Start

From the project root, run the CLI test workflow against your local dev server to verify backend changes.

Frequently Asked Questions about cli-backend-testing

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

FAQPage Schema
How do I automate end-to-end testing for TRPC routers against a local dev server?

Automating TRPC router testing involves using the LobeHub CLI to verify backend API changes against a local dev server. You can trigger the workflow with commands like 'cli test' to ensure API stability and correct responses.

What do I need to set up before running CLI-based backend integration tests?

Before running CLI-based backend integration tests, you need a running dev server at http://localhost:3011, the CLI source located at lobehub/apps/cli/, and authentication configured via the device-code flow using LOBEHUB_CLI_HOME=.lobehub-dev.

Can I test backend services and models without a running dev server?

Testing backend services and models requires a running dev server at http://localhost:3011. The CLI-based testing workflow verifies server-side changes by interacting directly with the local dev server to ensure accurate API validation.

What is the best way to validate server-side API changes after updating backend models?

The best way to validate server-side API changes is by running the CLI test workflow from the project root. This process tests TRPC routers, services, and models against your local dev server to confirm API stability.

Does the LobeHub CLI testing workflow support automated verification of services and models?

Yes, the LobeHub CLI testing workflow supports automated end-to-end verification of TRPC routers, services, and models. It validates backend changes by running CLI-based tests against your integrated local dev server environment.

Why does my backend API test require authentication via the device-code flow?

Backend API testing requires authentication via the device-code flow to securely authorize the CLI. You must set the environment variable LOBEHUB_CLI_HOME to .lobehub-dev to establish the proper authentication context for testing.