Skip to content
axxbetadocs
GitHub

Test with an agent

View .mdOpen in Claude

In this tutorial, we’ll give a coding agent an acceptance criterion in plain words and watch it write a scenario, check it and run it with Axx. Then we’ll review what it wrote.

We’ll use Claude Code and the hello-axx project from the Quickstart. You’ll need both.

In the hello-axx directory, install Axx’s skills:

Terminal window
axx skills install
Terminal window
installed 4 skills to .agents/skills (22 files updated)
linked for Claude Code in .claude/skills

The skills teach an agent how to find Axx’s steps, write a scenario, run it and read a failure. The AGENTS.md that axx init wrote in the Quickstart points agents at the same rules.

Start Claude Code in the project:

Terminal window
claude

Give it the criterion, not step text:

Add an acceptance test for this: asking for a file that doesn't exist returns 404. Use axx, and run it.

The agent’s wording will differ from run to run, but you’ll see it work through the same loop. Claude Code asks before each command, so you can follow along. Notice that it:

  1. checks the project with axx doctor;
  2. searches for real steps with axx steps search "response status code" instead of guessing their text;
  3. checks a line it’s unsure of with axx explain;
  4. writes a feature file;
  5. checks it with axx validate, starts the server with axx up, runs the scenarios with axx run --compact, and stops the server with axx down.

Open the feature file the agent created. In our run it was features/missing-file.feature:

features/missing-file.feature
Feature: Missing files
Asking for a file the service does not have is answered with Not Found.
Background:
Given the hello-axx service with the following properties:
| url | http://${sys:local.host}:8000 |
Scenario: Asking for a file that does not exist returns 404
Given a GET request to /no-such-file-404.json
When the request is executed
Then the response status code is 404

Read it against the criterion you gave. Each line says what it checks, so you can tell at a glance whether the agent tested what you asked for. That review is the part that stays yours.

Terminal window
axx run

The end of the output shows both scenarios, the Quickstart’s and the agent’s:

Terminal window
2 scenarios (2 passed)
9 steps (9 passed)

You gave an agent a criterion in plain words. It found the steps, wrote the scenario, checked it and ran it, and you confirmed it by reading it.

Set up agents connects other agents and Axx’s MCP server, and Axx for agents explains why Axx works this way.