Running Tests Manually

Running tests manually in Bruno allows you to quickly validate functionality and immediately view results. The most common example of this would be simply hitting an endpoint and seeing if it is working.

Running a Single Test

The smallest unit of testing in Bruno is a single request. The request itself tests the functionality of any given endpoint. You can add additional logic to requests by using the Tests tab.

To manually trigger a single test:

1. Open a Collection
2. Select the Request that you would like to run
3. Click Enter or press the send icon
4. View the results in the Tests section of the response pane

Running a Test Suite

Often times a Bruno Collection can represent a test suite of different actions or workflows of an API. You can use the Collection Runner to execute this entire suite, and also iterate through data using data driven testing.

Follow these steps to run your collection, view the results, and optionally download the test report as an HTML document.

1. Open the Bruno collection
2. Click on the Run option from the dropdown menu.

3. Click Run Collection to initiate the test.

4. Once the test run is complete, a test report will be automatically generated.

Download Test Report

After the test report is generated, you can download it as an HTML document (report.html).

1. Click the Download Report button to save the report.

Configuring a collection run

When you open the Collection Runner, you see a configuration view before starting the run. This view has two main areas: run settings on the left and request selection on the right.

Timings

Under the Timings section, set the Delay between requests (ms) to add a pause between each request execution. This is useful when working with rate-limited APIs.

Tag-based request filtering

Under the Filters section, you can filter which requests to include or exclude by tag.

1. Add tags to your requests: go to a request’s settings tab and add tags to categorize it.

2. Set include or exclude tags in the Filters section of the runner:
   • Include tags — only requests that have the specified tags will be eligible to run.
   • Exclude tags — requests that have the specified tags will be skipped.
   • A tag cannot appear in both lists at the same time.

When tag filters are active, requests that don’t match the criteria are automatically deselected in the request selection panel. Removing the tag filters re-selects them.

Learn more about tag filtering in Bruno CLI in the CLI tag filtering documentation.

Request selection and ordering

The right side of the configuration view lists all requests in the collection. You can:

• Select or deselect individual requests using checkboxes.
• Select All / Deselect All using the toggle at the top.
• Drag and drop requests to reorder the execution sequence.
• Reset the list to restore the original collection order and re-select all requests.

WebSocket and gRPC requests are not supported by the Collection Runner and appear disabled.

Your selection and ordering are preserved across sessions, so returning to the runner restores your previous configuration.

Filtering results

After a run completes, you can filter the results using the filter bar at the top of the results view:

• All — shows every executed request.
• Passed — shows only requests where all tests and assertions passed.
• Failed — shows only requests where any test or assertion failed, or an error occurred.
• Skipped — shows only requests that were skipped during execution.

Each filter button displays a count badge showing how many requests match that filter. You can click on a request’s status code to open a detailed response pane on the right side.

View Test Report

Once the report is downloaded, you can open the report.html file in any web browser to review the detailed test results.