Set up Test Engine with your coding agent

Setting up Test Engine used to mean choosing a framework and a CI provider, then copying steps into every job that runs tests. A coding agent can do that work from inside your repository, where it can read how your tests run, so Test Engine now lets you hand it the job.

On a repository that has never sent test results, Test Engine › Configuration opens on the setup:

• Let Your Agent Make the Change: open Claude Code or Cursor with a ready prompt, or copy it for another agent. The agent follows Mergify’s setup skill to find your test jobs and opens one pull request.
• Give Your CI Its Mergify Key: create the application key on the same page and store it in your CI as MERGIFY_TOKEN. The key never goes into the prompt.
• Do It by Hand: the same setup without an agent, with a Mergify plugin or with JUnit reports, folded away until you open it.
• Prevention and Detection: until the repository sends results, both pages say what they do and link to the setup. The agent also fills the gaps on a repository that already sends results. When some of your test jobs upload JUnit reports without the Mergify plugin, Native Flaky Detection on the same page names those jobs and offers “Install the Plugin”. It opens a panel with one prompt that adds the plugin to all of them in a single pull request, so Mergify can check those tests for flakiness too, and the steps by hand if you would rather do it yourself.

There is nothing to turn on: both show up on their own wherever they apply. Your agent writes the CI changes, and you review them like any other pull request.