Function test_instructions

mcp_server.py:742–862

Provide detailed instructions on running TEST_CASEs.

(
    arguments: dict[str, Any], project_root: Path
)

async def test_instructions(
    arguments: dict[str, Any], project_root: Path
) -> CallToolResult:
    """Provide detailed instructions on running TEST_CASEs."""

    instructions = """
# FastLED TEST_CASE Execution Guide

## Overview
FastLED uses the **doctest** framework for C++ unit testing. Tests are organized in files named `test_*.cpp` in the `tests/` directory. Each file can contain multiple `TEST_CASE` macros.

## Test Structure
- **Test Files**: Located in `tests/test_*.cpp` (e.g., `test_algorithm.cpp`, `test_easing.cpp`)
- **TEST_CASEs**: Individual test functions defined with `TEST_CASE("name")` macro
- **SUBCASEs**: Nested test sections within TEST_CASEs using `SUBCASE("name")`

## Running Tests

### 🚨 CRITICAL: Always Use `bash test` Format

**[OK] CORRECT Format:**
```bash
bash test                      # Run all tests
bash test <test_name>         # Run specific test
```

**[ERROR] INCORRECT Format:**
```bash
./.build/bin/test_<name>.exe  # DO NOT run executables directly
./tests/.build/bin/test_*     # DO NOT use this format
```

### 1. Run All Tests
```bash
bash test
```

### 2. Run Specific Test File
```bash
bash test <test_name>
```
Example: `bash test algorithm` (runs `test_algorithm.cpp`)
Example: `bash test audio_json_parsing` (runs `test_audio_json_parsing.cpp`)

### 3. Alternative: Using test.py directly
For advanced options, you can also use:
```bash
uv run test.py              # Run all tests
uv run test.py --cpp        # Run only C++ tests
uv run test.py --cpp <name> # Run specific test file
```

### 4. Run with Verbose Output
```bash
uv run test.py --cpp <test_name> --verbose
```

### 5. Using MCP Server Tools