> For the complete documentation index, see [llms.txt](https://testbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://testbox.ortusbooks.com/master-2/intro/release-history.md).

# Release History

In this section you will find the release notes for each version we release under this major version.  If you are looking for the release notes of previous major versions use the version switcher at the top left of this documentation book.  Here is a breakdown of our major version releases.

## Version 4.0 - April 2020

In this release we have dropped support for legacy CFML engines and introduced the ability  to mock data, relationships and build JSON documents.

## Version 3.0

In this release we focused on dropping engine supports for legacy CFML engines.  We had a major breakthrough in introducing Code Coverage thanks to the [FusionReactor](https://www.fusion-reactor.com/) folks as well.  This major release came also with a new UI for all reporters and streamlining the result view ports.

## Version 2.0

This version spawned off with over 8 minor releases.  We focused on taking TestBox 1 to yet a high level.  Much more attention to detail and introducing modern paradigms like given-when-then.  Multiple interception points, async executions and ability to chain methods.

## Version 1.0

This was our first major version for TestBox.  We had completely migrated from MXUnit and it introduced BDD to the ColdFusion (CFML) world.


---

# 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://testbox.ortusbooks.com/master-2/intro/release-history.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.