# Life-Cycle Events

![](/files/-MDzUwBF-QNcwr8ezc6K)

ColdBox testing leverages TestBox's testing life-cycle events (<https://testbox.ortusbooks.com/primers/testbox-bdd-primer/life-cycle-methods>) in order to prepare the virtual ColdBox application, request context and then destroy it. By default, a virtual application is loaded for all test cases contained within a test bundle CFC via the `beforeAll()` and destroyed under `afterAll()`.

```javascript
function beforeAll(){
    super.beforeAll();
    // do your own stuff here
}

function afterAll(){
    // do your own stuff here
    super.afterAll();
}
```

> **Important** If you override any of these methods and do not funnel the super call, then you might get cached or unexpected results.

## Improving Performance: Unloading ColdBox

The default for integration testing is that the virtual ColdBox application will be **destroyed** or **unloaded** in **each test**. To keep the virtual application **running across multiple test bundle** tests you will need to use the `unloadColdBox=false` annotation or the `this.unloadColdBox=false` setting in your `beforeAll()` method. This will stop the testing classes from destroying ColdBox and improving performance.

```javascript
component extends="coldbox.system.testing.BaseTestCase" unloadColdBox=false{
    
    this.unloadColdBox = false;
    
    function beforeAll(){
        super.beforeAll();
        // do your own stuff here
    }
}
```


---

# Agent Instructions: 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:

```
GET https://coldbox.ortusbooks.com/v6.x/testing/testing-coldbox-applications/integration-testing/life-cycle-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.