DAST

Managing agentic tests

• Last updated: November 5, 2026

• Read time: 3 Minutes

Check the progress of your agentic tests, review what Burp AT finds, and stop or delete tests.

Viewing your agentic tests

To view your tests, go to Agentic tests > Agentic tests.

Agentic test statuses

The status of a test tells you what you can do with it:

• Ready: The test is active. User-guided AI tests show this status. You can stop the test.
• In progress: The test is running. You can stop the test.
• Queued: Your instance is running as many agentic tests as it allows. Burp AT starts the test when another test finishes. For details, see Starting tests at the running-test limit.
• Finished: Goal met: Burp AT met the goal of the test.
• Failed: The test did not complete, or its environment failed. You can delete the test, but you cannot stop it.

Viewing scheduled agentic tests

To view tests that start later or repeat, go to Agentic tests > Scheduled agentic tests.

When a schedule has no more runs, Burp AT removes it from this list. The tests that the schedule ran stay in your list of agentic tests. To go from a test to the schedule that started it, open the test and click Visit schedule.

Reviewing issues and discovered URLs

To review what Burp AT has found, open the test from your list of agentic tests. Then go to the Issues or Discovered URLs tab.

Burp AT also adds its issues to the site, folder and global Issues lists. Burp AT does not add its issues to scan results or reports. Burp AT issues do not raise tickets in Jira or ServiceNow.

Stopping an agentic test

Stop a test when you no longer need it. If you do not stop a test, then its environment shuts down only after 24 hours without activity. While a test runs, you cannot delete its site or folder.

To stop a test:

1. Go to Agentic tests > Agentic tests.
2. Find the test with the status Ready or In progress.
3. Click the stop icon in the Actions column.
4. Confirm that you want to stop the test.

You need the Use agentic testing permission on the site to stop a test. Stopping a test shuts down its environment and pauses the work. To continue the work, see Restarting a stopped test.

Restarting a stopped test

To restart a stopped or inactive test, open it from your list of agentic tests. Burp AT starts the environment of the test. You can chat with Burp AT straight away. Burp AT runs tools when the environment is ready.

If the environment of a test failed, then opening the test does not restart it. Click Try again to start the environment.

Starting tests at the running-test limit

Your instance can run a limited number of agentic tests at once. A test counts as running while it is waiting to start, starting, ready or reconnecting. Stopped, failed and finished tests do not count. To start another test, stop a test that you no longer need, or wait for one to finish.

When your instance reaches the limit:

• You cannot create a User-guided AI test.
• You can create and schedule a Full AI autonomy test, including one that starts as soon as possible. Burp AT gives the test the status Queued and starts it when another test finishes.
• Burp AT also gives the status Queued to a scheduled test that is due to start.
• You can open a stopped or failed test, but you cannot start it until another test finishes.

Deleting agentic tests

Delete a test to remove it from your list. To delete a test, click the trash can icon in the Actions column, then confirm. You can also click Delete test on the test page.