> For the complete documentation index, see [llms.txt](https://docs.liquidapps.io/liquidapps-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquidapps.io/liquidapps-documentation/working-with-zeus-sdk/zeus-basics/testing/printing-console.md).

# Printing Console

When working with eosio smart contracts you can print to console with `eosio::print();`

You can access this with the following logic in your unit test to log console following an action, or when an error is caught to log it as well:

```javascript
try {
    // ... other stuff
    const res = await deployedContract.action({
        params...
    }, {
      authorization: `${code}@active`,
      broadcast: true,
      sign: true
    });
    console.log(`console: ${res.processed.action_traces[0].console}`);
    done();
}
catch (e) {
    if(e && e.error && e.error.details && e.error.details[1]) {
        console.log(e.error.details[1].message);
    }
    done(e);
}
```

And in your contract:

```cpp
[[eosio::action]] void action(
  params...
) {
  eosio::print("hello from eosio");
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.liquidapps.io/liquidapps-documentation/working-with-zeus-sdk/zeus-basics/testing/printing-console.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.