> 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/integration-testing/testing-without-virtual-application.md).

# Testing Without Virtual Application

Set this.loadColdBox = false to use BaseTestCase for unit testing without loading the virtual application.

The `BaseTestCase` leverages an internal virtual ColdBox application so you can do integration testing. Meaning that whenever you extend from the `BaseTestCase` the virtual ColdBox will be loaded. However, you can tell the testing framework to **NOT** load it by using the `this.loadColdBox` variable:

{% tabs %}
{% tab title="BoxLang" %}

```js
class extends="coldbox.system.testing.BaseTestCase"{
    // Do not load the Virtual Application
    this.loadColdBox = false;
}
```

{% endtab %}

{% tab title="CFML" %}

```cfscript
component extends="coldbox.system.testing.BaseTestCase"{
    // Do not load the Virtual Application
    this.loadColdBox = false;
}
```

{% endtab %}
{% endtabs %}

This is a great approach if you still want to leverage the base test case for unit testing but without loading the entire virtual application.


---

# 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/integration-testing/testing-without-virtual-application.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.