# Output Utilities

Sometimes you will need to produce output from your tests and you can do so elegantly via some functions we have provided that are available in your test bundles:

* `console(var, top=[9999])` - Send data to the console via `writeDump( output="console" )`
* `debug(var, label="", deepCopy=[false], top=999)` - Send data to the TestBox debug stream, will be saved in the test results and outputted in reports
* `print( message )` - Write some output to the ColdFusion output buffer
* `println( message )` - Write some output to the ColdFusion output buffer and appends a newline character

These are great little utilities that are needed to send output to several locations.

> **Hint** Please note that the `debug()` method does **NOT** do deep copies by default.

```javascript
console( myResults );

debug( myData );
debug( myData, true );

debug( var=myData, top=5 );

print( "Running This Test with #params.toString()#" );
println( "Running This Test with #params.toString()#" );
```


---

# 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://testbox.ortusbooks.com/v2.x-1/in-depth/output-utilities.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.