Resources
Playbooks, guides, and best practices for AI-native E2E testing.
Spec-Driven Development with GitHub Spec Kit: A Practical Workflow
A step-by-step guide to the GitHub Spec Kit workflow: install the specify CLI, then move through constitution, specify, plan, tasks, and implement. Learn what each command produces and how to close the one gap Spec Kit leaves open: proving the built software matches the spec.
When Agents Write the Code, the Spec Is the Source of Truth
Once a coding agent can regenerate an implementation on demand, the code stops being the durable thing you maintain. What lasts is the spec plus the verification that proves the code still satisfies it.
Test-Driven Development in the AI Era
Test-driven development still works when an agent writes your code, but the order of operations changes. Classic TDD assumes a human writes the failing test first; when the agent produces the implementation in seconds, the human can no longer lead with tests. The AI-era loop keeps the test as the source of truth while the agent generates code and verification together, checked against intent, so the regression suite grows as a byproduct of building.
How to Test Apps Built with v0, Lovable, and Bolt
AI app builders generate a working-looking UI in minutes, but nothing in that loop proves the flows behave correctly or keep behaving after the next generation. This guide covers where verification belongs, when to add it, and the workflow for turning generated code into an app with maintained end-to-end tests.
Tests Are the Best Context You Can Give a Coding Agent
A coding agent guesses at what 'working' means unless something tells it. Tests in the repo are that something: they define the target, catch mistakes the moment they happen, and let the agent fix itself before a human ever looks. Here is why tests are the highest-signal context you can hand an agent, and what good agent-readable tests look like.
Verification-Driven Development: Building Software Agents Can Prove
Verification-driven development (VDD) is a methodology where every change ships with proof it behaves correctly, and that proof is generated as a byproduct of building, not a separate phase afterward. This guide defines VDD, traces its lineage from shift-left and spec-driven development, contrasts it with test-after and code-review-only workflows, and shows why the agent era makes it necessary.