> For the complete documentation index, see [llms.txt](https://developer.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.openactive.io/open-booking-api/test-suite.md).

# Testing booking

Testing your booking system is essential and leads to two important outcomes:

1. It checks that your system meets OpenActive standards, works smoothly, and avoids common issues.
2. It gives you a certificate showing you meet these standards, which will encourage others to integrate with your system, leading to more bookings.

## Prerequisites for testing

In order to run tests, you must first have implemented:

* Booking ([Implementing booking](/open-booking-api/implementing-booking.md)).
* Some or all of the [OpenActive Test Interface](https://openactive.io/test-interface/).
  * The [Datasets Endpoints](https://openactive.io/test-interface/#datasets-endpoints) are needed if using [Key Decisions](/open-booking-api/key-decisions.md#controlled-mode).
  * The [Actions Endpoint](https://openactive.io/test-interface/#actions-endpoint) are needed if any of the actions are required to test features that you have implemented.

## Test Suite Overview

The [OpenActive Test Suite](https://github.com/openactive/openactive-test-suite/) consists of two key components:

* [**openactive-broker-microservice**](https://github.com/openactive/openactive-test-suite/tree/master/packages/openactive-broker-microservice) - harvests feeds and provides an interface to extract specific items from the feeds.
* [**openactive-integration-tests**](https://github.com/openactive/openactive-test-suite/tree/master/packages/openactive-integration-tests) - a suite of Jest integration tests that exercise an Open Booking API implementation.

## What to do

Work through each of the steps in this guide, by following the "Next" button below.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.openactive.io/open-booking-api/test-suite.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.