> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/the-basics/testing-quick-start/coldbox-testing-classes.md).

# Testing Classes

ColdBox testing classes: BaseTestCase for integration tests plus BaseModelTest, BaseInterceptorTest, BaseHandlerTest, plus browser testing on BoxLang with the @browser annotation.

![ColdBox Testing Classes](https://content.gitbook.com/content/XMVfvHPJ9ZanT1mSFxLz/blobs/gRuExDQ4BljvOhwFqWnh/TestingClasses.png)

Before we begin our adventures in testing, let's review what classes ColdBox gives you for testing and where you can find them. From the diagram, you can see that our pivot class for testing is the TestBox `BaseSpec` class.

From that superclass, we have our own ColdBox `BaseTestCase` , our base class for any testing in ColdBox, and the class used for Integration Testing. We then spawn several child classes for targeted testing of different objects in your ColdBox applications:

<table><thead><tr><th width="260">Test Class</th><th>Description</th></tr></thead><tbody><tr><td><code>BaseTestCase</code></td><td>Used for Integration Testing</td></tr><tr><td><code>BaseModelTest</code></td><td>Used for model object unit testing</td></tr><tr><td><code>BaseInterceptorTest</code></td><td>Used for interceptor unit testing</td></tr><tr><td><code>BaseHandlerTest</code></td><td>Used for isolated handler unit testing</td></tr></tbody></table>

{% hint style="info" %}
🚀 **Browser Testing (BoxLang)**: there is no separate browser test class. Add the `@browser` annotation (or `@browserProfile` or `@baseURL`) to a `BaseTestCase` spec, or any other spec, and TestBox drives a real browser against your running application with bx-playwright. `BaseTestCase` provides the named route helpers `routeURL()`, `visitRoute()` and `assertRouteIs()`. Browser specs are BoxLang classes and need the bx-playwright module, so keep them in their own folder and exclude it from the runner on CFML engines. See [Browser Testing](/the-basics/testing-quick-start/browser-testing.md).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox.ortusbooks.com/the-basics/testing-quick-start/coldbox-testing-classes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.