Search
Best Practices
How to use Studio well: picking the right candidates, keeping the testing agent independent of the building agent, writing prompts that last, and stopping a good suite from rotting.
-
What Makes a Good Automation Candidate
The single most expensive mistake in test automation is not a bad tool. It is automating the wrong things, discovering it six months later, and concluding that automation does not work. Open in Studio Your existing projects and tests, to score against. ...
-
Writing Prompts That Produce Durable Tests
The quality of a Studio test is decided almost entirely in the sentence you write to ask for it. Not by the tool, not by the application, and not by how long you spend editing afterward. Open in Studio Try a prompt for real. Links open in a new tab. St...
-
Reviewing AI-Generated Tests: What a Human Still Has to Check
An agent can write a test faster than you can read one. That asymmetry is the productivity gain, and it is also the risk: it is entirely possible to acquire four hundred tests in a week, none of which would notice if checkout broke. Open in Studio Open ...
-
The Independent Tester Principle: Never Build and Test in the Same Session
If you take one practice away from this section, take this one: never let the same AI session that wrote the code also write and judge the tests for it. Open in Studio Where the independent tests end up. Links open in a new tab. Studio Home ↗Tests ↗MCP...
-
Setting Up an Adversarial Test Loop With Claude and the Functionize MCP Server
The previous page argues that the agent which wrote the code must not be the agent which tests it. This page is the setup: two sessions, two models, one of them pointed at Functionize over MCP, and a loop that runs every time you ship. Open in Studio Se...
-
Keeping a Suite Green: Flake, Tiers and Who Owns Red
Most suites do not fail all at once. They erode: a test that fails intermittently gets rerun instead of fixed, then another, then the team learns that red usually means nothing, and within a quarter nobody reads the result at all. The suite still runs. ...