mcp-server-langgraph: Command for Claude Code

Quick Test Status Check

Usage: /test-status or /test-status <marker>

Markers: Any pytest marker (e.g., unit, integration, api, security)

---

🎯 Purpose

Provides a fast, lightweight status check of tests without running comprehensive analysis.

Use this for:

• Quick validation during development
• Rapid feedback after code changes
• Fast status checks before commits

For comprehensive analysis, use /test-summary instead.

---

⚡ Quick Status Check

Step 1: Determine Scope

Based on $ARGUMENTS, determine which tests to check:

Default (all tests):

pytest -v --tb=line --no-cov -q

Specific marker (e.g., /test-status unit):

pytest -m $ARGUMENTS -v --tb=line --no-cov -q

Options used for speed:

• --no-cov - Skip coverage (faster)
• -q - Quiet mode (less output)
• --tb=line - Minimal traceback (faster display)
• -x - Stop on first failure (optional, for even faster feedback)

---

Step 2: Run Fast Test Check

Execute tests with minimal overhead:

# Run tests without coverage
pytest -v --tb=line --no-cov -q 2>&1 | tee /tmp/test_status.txt

# Capture exit code
TEST_EXIT=$?

Capture:

• Total tests run
• Pass/fail count
• First failure (if any)
• Total duration

---

Step 3: Parse Results

Extract key metrics from output:

# Parse pytest output for summary line
# Example: "437 passed in 12.34s"
# Example: "425 passed, 12 failed in 23.45s"

SUMMARY=$(tail -n 5 /tmp/test_status.txt | grep -E "passed|failed|skipped")

---

Step 4: Display Quick Status

Show concise status report:

## ⚡ Test Status

**Status**: ✅ PASSING | ❌ FAILING | ⚠️ ISSUES

**Quick Summary**:
- Passed: XXX
- Failed: XX
- Skipped: XX
- Duration: XX.Xs

**Scope**: [all|unit|integration|$MARKER]

---

[If all passing]:
✅ **All tests passing** - Ready to proceed

[If failures]:
❌ **Tests failing** - Fix before proceeding
First failure: `test_name` in `file_path.py:line`

Run `/test-summary` for detailed failure analysis.

[If skipped tests]:
⚠️ **XX tests skipped** - May need infrastructure
Run with `-v` to see skip reasons.

---

**Quick Commands**:

Run failed tests only:
```bash
pytest --lf -x  # Stop on first failure

Run specific test:

pytest tests/path/test_file.py::test_name

Fast iteration:

make test-dev  # Fast mode (40-70% faster)

---

Next Steps:

✅ All passing → Proceed with commit/deployment ❌ Failures → Run /test-summary failed for analysis ⚠️ Skipped → Check infrastructure (docker compose up)

For comprehensive analysis: /test-summary For test debugging: /fix-issue <test-name>