> 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/v2.x-1/introduction/installing-testbox.md).

# Installing TestBox

TestBox can be downloaded from <https://www.ortussolutions.com/products/testbox> or can be installed via [CommandBox CLI](https://www.ortussolutions.com/products/commandbox). CommandBox is our preferred approach for all package installations, updates and more.

```javascript
// latest stable version
box install testbox --saveDev

// latest bleeding edge
box install testbox@be --saveDev
```

> **Note** Please note the `--saveDev` flag which tells CommandBox that TestBox is a development dependency and not a production dependency.

This will install TestBox in a */testbox* folder from where you called the command. You can also extract the download zip and place it anywhere you like and create a mapping called */testbox* that points to testbox in the distribution folder, this is the most secure approach. However, you can just place it in the webroot if you like.

```javascript
this.mappings[ "/testbox" ] = expandPath( "C:/frameworks/testbox/" );
```

You can also clone from [Github](https://github.com/ortus-solutions/testbox) and help us out :)

```javascript
git clone git://github.com/ortus-solutions/testbox testbox
```


---

# 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/v2.x-1/introduction/installing-testbox.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.