> 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/readme/release-history.md). # Release History A brief history of TestBox 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 7.x - March 2026 In this release, we focused on BoxLang CLI runner enhancements, real-time streaming test execution via SSE, a powerful dry run capability for spec discovery, Lucee 7 certification, and dropping Adobe 2021 support. Developers gain a wealth of new output-control and performance-analysis options directly from the CLI runner. The **7.1** minor release builds on that foundation with a major expansion of the assertions and expectations library: grouped assertions, collection expectation modes, expectation context for richer failure messages, and dedicated matcher families for BoxLang `Set` and `Range` objects plus a data navigator for asserting against deeply nested structures. The **7.2** minor release brings browser testing to TestBox: BoxLang specs with a `@browser` annotation drive a real browser through the [bx-playwright](https://bxplaywright.boxlang.io) module, with web-first browser matchers and the screenshots, traces and videos of failures attached to the spec. Every suite, on every engine, also gains spec attachments, spec retries and a **Run Failed** option, plus BoxLang runner options to start a web server for the run. The **HTML reporters** get a complete new look, with light and dark themes, keyboard navigation and **Ask AI**, which hands any failure to ChatGPT, Claude or your coding agent in one click. It also adds the **Agent reporter**, a compact JSON reporter built for AI agents and automation that reports the totals plus only the failing specs. ## Version 6.x - September 2024 In this release, we have dropped more legacy engines and added full support for not only running TestBox in [BoxLang](https://www.boxlang.io/), but writing every spec in [BoxLang](https://www.boxlang.io/). We have added tons of bug fixes and major improvements but also a great CLI runner for BoxLang. ## Version 5.x - May 2023 In this release, we have dropped legacy engines and added support for the [BoxLang](https://www.boxlang.io) JVM language, Adobe 2023 and Lucee 6. We have also added major updates to spying and expectations. We continue in this series to focus on productivity and fluency in the Testing language in preparation for more ways to test. ## Version 4.x - April 2020 In this release, we have dropped support for legacy CFML engines and introduced the ability to mock data and relationships and build JSON documents. ## Version 3.x 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 also came with a new UI for all reporters and streamlined the result viewports. ## Version 2.x 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.x This was our first major version of 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://testbox.ortusbooks.com/readme/release-history.md?ask=&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.