> 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/getting-started/installing-testbox/ide-tools.md).

# IDE Tools

A modern editor can enhance your testing experience. We maintain editor integrations that help you write, navigate, and run TestBox tests.

## VSCode Plugin

The VSCode plugin is the best way for you to interact with TestBox alongside the BoxLang plugin. It allows you to run tests, generate tests, navigate tests and much more.

<figure><img src="https://content.gitbook.com/content/5kuiG5ZXNT2hNA83299A/blobs/UforLm5nKgp2rin0Sias/image.png" alt=""><figcaption></figcaption></figure>

{% embed url="<https://marketplace.visualstudio.com/items?itemName=ortus-solutions.vscode-boxlang>" %}
BoxLang
{% endembed %}

{% embed url="<https://marketplace.visualstudio.com/items?itemName=ortus-solutions.vscode-testbox>" %}
TestBox
{% endembed %}

## Sublime Text Package

The [BoxLang Sublime Text package](https://boxlang.ortusbooks.com/getting-started/ide-tooling/boxlang-sublime-text) adds BoxLang syntax highlighting, completions, inline documentation, and a native TestBox runner to Sublime Text 4.

Install **BoxLang** through Package Control. With TestBox 7 or later available in your project, use the Command Palette to run the current bundle, the spec or suite at the cursor, all tests, or repeat the last run. The package uses the BoxLang CLI runner by default and can also run tests through a configured HTTP runner.

Syntax highlighting works without BoxLang. The full feature set requires BoxLang CLI 1.17 or later, and the TestBox runner requires TestBox 7 or later. See the [TestBox BoxLang CLI Runner guide](/getting-started/running-tests/boxlang-cli-runner.md) for runner details, and the [Sublime Text package repository](https://github.com/ortus-boxlang/sublimetext-boxlang) for installation and configuration options.


---

# 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/getting-started/installing-testbox/ide-tools.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.