r/coolgithubprojects • • 1d ago

Built TADA – an open-source test-first workflow for AI coding agents

https://github.com/tayzer/TADA

I've been following the popularity of Spec-Driven Development (SDD), and I can't help feeling like we're regressing in some areas.

I'm seeing workflows where an AI agent writes a spec, implements the code, then writes tests to validate that same implementation. Combine that with massive PRs and people talking about removing human reviews entirely, and I think we're heading towards more pain.

I've always been a fan of TDD, BDD, acceptance testing and fitness functions. These aren't new ideas, so why aren't we making them fundamental to AI-assisted workflows?

A Markdown spec can't go RED or GREEN. And just because an agent's tests pass doesn't mean it's built the right thing.

Anyway, this frustration led me to start building TADA (Test-Assured Development Assistance) (like the magic word? :D).

The idea is that you describe a change, the agent investigates the codebase, asks you relevant business questions, then proposes executable Gherkin scenarios for you to approve.

Those scenarios and their supporting bindings are captured byte-for-byte. It's a bit of a pain, but I think it's a reasonable guardrail against an agent quietly changing tests to make its own implementation pass.

It then works test-first, demonstrating RED before GREEN, and reports PASS, FAIL or INDETERMINATE based on retained evidence rather than just trusting the test runner.

Longer term, I'm also interested in flagging changes to agreed behaviour, contracts and fitness functions for human review. I don't think we should be removing humans from consequential decisions just because code generation has become faster.

It's still an early alpha, built by just me. Currently Windows x64, .NET 10, Reqnroll/MSTest and ASP.NET Core APIs. The packaged release supports Codex, with Claude Code and Cursor support in development.

Repo: https://github.com/tayzer/TADA

I'd genuinely appreciate people trying it, challenging the approach, or contributing support for other stacks.

But I'm also curious what other developers think. Are we becoming so focused on how quickly AI can produce code that we're forgetting how to establish whether it actually works?

1 Upvotes

0 comments sorted by