gtest-tdd-loop
Gtest Tdd Loop
Overview
Drive local verification through a red-green loop and summarize failures in a machine-readable form.
Start Here
Read ../../references/gtest-cheatsheet.md, ../../references/sails-gtest-and-local-validation.md, and ../../references/gear-gas-reservations-and-waitlist.md.
Use ../../assets/gtest-report-template.md as the output shape.
Write the result to docs/plans/YYYY-MM-DD-<topic>-gtest.md.
Use ../../scripts/run_gtest.sh to execute the loop and ../../scripts/parse_test_output.py to summarize failures.
Workflow
- Write or update the smallest failing gtest case for the current task.
- Verify the test fails for the expected reason.
- Apply the minimal implementation change.
- Run the local loop through
../../scripts/run_gtest.sh. - Capture the parser output and record the final green or remaining gap state.
Guardrails
- Do not skip the failing-test step.
- Do not claim success from compile output alone.
- Keep gtest evidence tied to the current task, not a generic workspace run.
- Escalate if the workspace cannot produce a stable local gtest target.
More from gear-foundation/vara-skills
vara-skills
Use when a builder needs the top-level router for the provisional standard Gear/Vara Sails skill pack across Codex, Claude, or OpenClaw. Do not use for Vara.eth or ethexe work, non-Sails programs, or broad protocol research.
194sails-new-app
Use when a builder is starting a new standard Gear/Vara Sails app and needs the correct greenfield sequence before implementation. Do not use for edits to an established repo, Vara.eth or ethexe targets, or non-Sails templates.
2sails-dev-env
Use when a builder needs to prepare or repair a local macOS, Linux, or Windows machine for standard Gear/Vara Sails Rust development before building, testing, or running a local node. Do not use for live-network deployment, app-specific feature work, or Vara.eth/ethexe-only setup.
2vara-wallet
Use when an agent needs to interact with Vara Network on-chain — deploy programs, call Sails methods, manage wallets, transfer tokens, monitor events. Not for building Sails programs (use vara-skills for that).
2sails-gtest
Use when a builder needs the standard Gear/Vara Sails gtest loop for feature verification, debugging, or regression coverage. Do not use for live-network-only validation, deployment-first workflows, or non-Sails programs.
2task-decomposer
Use when approved spec and architecture artifacts must become an ordered implementation plan for Gear or Vara work. Do not use when the architecture is still unsettled or when the request is only asking for a high-level idea.
2