# Tddkind > TDD workflow with Kind cluster - fast local iteration for Kagenti development Use when this capability is needed. - Skill: `tomevault-io/tddkind` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/tddkind` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/tddkind/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/tddkind --- # TDD-Kind Workflow Test-driven development workflow using a local Kind cluster for fast iteration. ## When to Use - Reproducing CI Kind failures locally - Testing changes before pushing to CI - Fast feedback loop without HyperShift cluster overhead - Debugging Ollama/agent issues in Kind environment > **Auto-approved**: All operations on Kind clusters (read + write, deploy, test) are auto-approved. > Cluster create/destroy is also auto-approved for Kind. ## Cluster Concurrency Guard **Only one Kind cluster at a time.** Before any cluster operation, check: ```bash kind get clusters 2>/dev/null ``` - **No clusters** → proceed normally (create cluster) - **Cluster exists AND this session owns it** → reuse it (skip creation, run tests) - **Cluster exists AND another session owns it** → **STOP**. Do not proceed. Inform the user: > A Kind cluster is already running (likely from another session). > Options: (a) wait for that session to finish, (b) switch to `tdd:ci` for CI-only iteration, (c) explicitly destroy the existing cluster first with `kind delete cluster --name kagenti`. To determine ownership: if the current task list or conversation created this cluster, it's yours. Otherwise assume another session owns it. ```mermaid flowchart TD START(["/tdd:kind"]) --> GUARD{"kind get clusters"} GUARD -->|No clusters| CREATE["Create Kind cluster"]:::k8s GUARD -->|Cluster exists, mine| REUSE["Reuse existing cluster"]:::k8s GUARD -->|Cluster exists, not mine| STOP([Stop - another session owns it]) CREATE --> CVEGATE["CVE Gate: cve:scan"]:::cve REUSE --> CVEGATE CVEGATE -->|Clean| ITER CVEGATE -->|CVE found| CVE_HOLD["cve:brainstorm"]:::cve CVE_HOLD -->|Resolved| ITER ITER{"Iteration level?"} ITER -->|Level 1| L1["Test only (fastest)"]:::test ITER -->|Level 2| L2["Reinstall + test"]:::test ITER -->|Level 3| L3["Full cluster recreate"]:::test L1 --> CHECK{"Tests pass?"} L2 --> CHECK L3 --> CHECK CHECK -->|Yes| BRANCHCHECK{"Branch verified?"} CHECK -->|No, minor| FIX["Fix code"]:::tdd CHECK -->|No, env issue| ITER BRANCHCHECK -->|Yes| COMMIT["git:commit"]:::git BRANCHCHECK -->|Wrong branch| WORKTREE["Create worktree"]:::git WORKTREE --> COMMIT FIX --> L1 COMMIT --> DONE([Push to CI / tdd:ci]) classDef tdd fill:#4CAF50,stroke:#333,color:white classDef rca fill:#FF5722,stroke:#333,color:white classDef git fill:#FF9800,stroke:#333,color:white classDef k8s fill:#00BCD4,stroke:#333,color:white classDef hypershift fill:#3F51B5,stroke:#333,color:white classDef ci fill:#2196F3,stroke:#333,color:white classDef test fill:#9C27B0,stroke:#333,color:white classDef cve fill:#D32F2F,stroke:#333,color:white ``` > Follow this diagram as the workflow. ## CVE Gate (Pre-Deploy) **MANDATORY before deploying to Kind cluster.** Invoke `cve:scan` on the working tree before the first deployment: 1. If `cve:scan` returns clean → proceed to iteration selection 2. If `cve:scan` finds HIGH/CRITICAL CVEs → `cve:brainstorm` activates a CVE hold - Silent fixes (dependency bumps) are allowed - Deployment proceeds only after hold is resolved This gate runs once per session, not on every iteration. ## Key Principle **Match CI exactly**: Kind tests must use the same packages as CI to avoid version mismatches. CI uses `pip install` (gets latest versions), local uses `uv` (locked versions). Always verify package versions match. ## Context-Safe Execution (MANDATORY) **Every command that produces more than ~5 lines of output MUST redirect to a file.** ```bash # Session-scoped log directory — use worktree name to avoid collisions export LOG_DIR="${LOG_DIR:-${WORKSPACE_DIR:-/tmp}/kagenti-tdd}" mkdir -p "$LOG_DIR" ``` ### Log Analysis Rule **NEVER read large log files in the main context.** Always use subagents: 1. Note the log file path and exit code 2. Use `Task(subagent_type='Explore')` to read the log and extract relevant info 3. The subagent returns a concise summary (errors, unexpected output, specific data) 4. **Use subagents for success analysis too** — e.g., "verify test output shows expected pass count" 5. Fix or proceed based on the summary ## Quick Start ```bash # Create Kind cluster and deploy (first time) ./.github/scripts/local-setup/kind-full-test.sh --skip-cluster-destroy > $LOG_DIR/kind-setup.log 2>&1; echo "EXIT:$?" # Run tests only (cluster already exists) ./.github/scripts/local-setup/kind-full-test.sh --include-test > $LOG_DIR/kind-test.log 2>&1; echo "EXIT:$?" # Run specific tests ./.github/scripts/local-setup/kind-full-test.sh --include-test --pytest-filter "test_agent" > $LOG_DIR/kind-test.log 2>&1; echo "EXIT:$?" # Run from worktree .worktrees/my-feature/.github/scripts/local-setup/kind-full-test.sh --include-test > $LOG_DIR/kind-test.log 2>&1; echo "EXIT:$?" ``` ## TDD Iterations ### Iteration 1: Test only (fastest) ```bash ./.github/scripts/local-setup/kind-full-test.sh --include-test > $LOG_DIR/iter1-test.log 2>&1; echo "EXIT:$?" ``` ### Iteration 2: Reinstall + test ```bash ./.github/scripts/local-setup/kind-full-test.sh \ --include-uninstall --include-install --include-agents --include-test \ > $LOG_DIR/iter2-reinstall.log 2>&1; echo "EXIT:$?" ``` ### Iteration 3: Full cluster recreate ```bash ./.github/scripts/local-setup/kind-full-test.sh --skip-cluster-destroy > $LOG_DIR/iter3-full.log 2>&1; echo "EXIT:$?" ``` ## Reproducing CI Failures ### Step 1: Check CI package versions ```bash # Get the CI run logs and find installed versions (redirect to file) gh run view --log > $LOG_DIR/ci-log.txt 2>/dev/null; grep "Successfully installed" $LOG_DIR/ci-log.txt | tr ',' '\n' | sort ``` ### Step 2: Compare with local ```bash # Check local locked version grep '' uv.lock | head -3 # Check what uv uses uv run pip show | grep Version ``` ### Step 3: Pin if mismatched If CI has a different version than local: ```bash # Option A: Pin in pyproject.toml # Change: "a2a-sdk>=0.2.5" to "a2a-sdk==0.3.19" # Option B: Update uv.lock to match CI uv lock --upgrade-package a2a-sdk ``` ### Step 4: Run locally like CI ```bash # Run with pip (like CI) instead of uv to reproduce exactly python -m venv /tmp/ci-test-env source /tmp/ci-test-env/bin/activate pip install -e ".[test]" pytest kagenti/tests/e2e/common -v --timeout=300 deactivate ``` ## Kind Environment Details | Component | Value | |-----------|-------| | LLM | Ollama `qwen2.5:3b` via dockerhost:11434 | | Agent URL | http://localhost:8000 (port-forward) | | Backend URL | http://localhost:8002 (port-forward) | | Keycloak | http://keycloak.localtest.me:8080 | | MLflow | Disabled in Kind (dev_values.yaml) | | Phoenix | http://phoenix.localtest.me:8080 | | Kiali | http://kiali.localtest.me:8080 | ## Show Services ```bash ./.github/scripts/local-setup/show-services.sh # compact ./.github/scripts/local-setup/show-services.sh --verbose # full details ``` ## Debugging Agent Issues ```bash # Check agent pod (redirect to file) kubectl get pods -n team1 > $LOG_DIR/pods-team1.log 2>&1 && echo "OK" || echo "FAIL" # Agent logs (redirect to file) kubectl logs -n team1 -l app.kubernetes.io/name=weather-service --tail=50 > $LOG_DIR/agent.log 2>&1 && echo "OK" || echo "FAIL" # Check Ollama (small output, OK inline) curl -s http://localhost:11434/api/tags | jq -r '.models[].name' # Check port-forward (small output, OK inline) ps aux | grep port-forward | grep -v grep ``` Use `Task(subagent_type='Explore')` to analyze `$LOG_DIR/agent.log` if issues are found. ## Common Issues ### Agent empty response - Check Ollama model is loaded: `curl http://localhost:11434/api/tags` - Check model supports tool calling (need >= 3B for qwen2.5) - Check agent logs for LLM errors ### Package version mismatch with CI - CI uses `pip install` (latest versions) - Local uses `uv` (locked versions) - Pin versions in pyproject.toml or update uv.lock ### MLflow tests skipped - MLflow is disabled in Kind (dev_values.yaml) - MLflow trace tests are OpenShift-only ## UI Tests For Playwright UI tests (login, navigation, agent chat), invoke `test:ui`. Tests run against the Vite dev server which proxies `/api` to `localhost:8000` (backend port-forward). ## Session Reporting After the TDD workflow completes (CI green and PR approved/merged), invoke `session:post` to capture session metadata: 1. The skill auto-detects the current session ID and PR number 2. Posts a session report comment with token usage, skills used, and workflow diagram 3. Updates the pinned summary comment This is optional but recommended for tracking development effort. ## Related Skills - **`test:ui`** - **Write and run Playwright UI tests** - **`tdd:ci`** - CI-driven TDD (wait for CI results) - **`tdd:hypershift`** - TDD with HyperShift cluster - **`kind:cluster`** - Create/destroy Kind clusters - **`k8s:live-debugging`** - Debug on running cluster - `test:run-kind` - Run tests on Kind - `test:review` - Review test quality - `git:commit` - Commit format - `session:post` - Post session analytics to PR - `cve:scan` - CVE scanning gate (pre-deploy) - `cve:brainstorm` - CVE disclosure planning (if CVEs found) --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/kagenti) — claim your Tome and manage your conversions.