Resources
Playbooks, guides, and best practices for AI-native E2E testing.
How to Test Code Written by Antigravity CLI (and Gemini CLI Before It)
Google retired Gemini CLI on 18 June 2026 and replaced it with Antigravity CLI. The verification loop is the same either way: run the change in a real browser, save the check as a durable E2E test, and gate every merge in CI.
How to Verify AI-Generated Code: A Practical Checklist
Verifying AI-generated code means proving the change does what it was asked to do, not just that it reads well and passes unit tests. This checklist walks the full sequence: static review, unit tests, integration and contract checks, behavioral verification in a real browser, and a regression test that stays green. The behavioral step is the one most teams skip, and it is where the failures that reach users hide.
How to Use MCP for Test Automation: A Workflow
MCP lets a coding agent call browser and testing tools directly while it builds, instead of switching to a separate dashboard. This is the end-to-end workflow: install an MCP server, let the agent drive a real browser, verify changes, author tests, triage failures, and run the suite in CI.
The Regression Risk of AI-Generated Code (and How to Contain It)
AI coding agents edit broadly and fast, so each change touches more surface and the odds of silently breaking a working flow go up. This analysis explains why AI edits raise regression risk, the specific failure modes to watch, and how to contain them with regression coverage that grows as fast as the code.
Spec-Driven Development with AI Coding Agents
Spec-driven development gives an AI coding agent a written spec as both the input that drives code generation and the definition of what done means. This guide walks the practical loop: write the spec, let the agent implement, verify the output against the spec, and turn acceptance criteria into regression tests.
Spec-Driven Development vs Test-Driven Development
Spec-driven development and test-driven development both make intent executable before code, but at different altitudes. This guide compares SDD, TDD, and BDD by what gets written first, who authors it, and what it verifies, then shows where each one stops.