> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/victa/how-tos/how-to-test-the-onboard-printer.md).

# How to Test the Onboard Printer

Run a test print on your Victa to check the printer is working.

{% hint style="info" %}
**Use this when** you want to check the printer is working — for example, if receipts aren't printing.
{% endhint %}

{% stepper %}
{% step %}

### Check the paper roll

Make sure a paper roll is fitted correctly. Open the printer cover, insert the roll, leave a small piece of paper sticking out, and close the cover.
{% endstep %}

{% step %}

### Open Diagnostics

1. Open the app list: swipe **up** on the home screen. If your Victa opens straight into **Connect Express**, swipe **down** from the top of the screen and tap the **settings icon** in the bottom-right corner to get to the Android menu.
2. Tap **Diagnostics**.
   {% endstep %}

{% step %}

### Run a test print

Tap **Summary**, then tap **Test print** next to **Printer status**. You can also run a test print from **Peripherals information**.
{% endstep %}
{% endstepper %}

**If the test print fails,** see [Printer Not Working](/support-nordics/victa/errors/printer-not-working.md).

<details>

<summary>Keywords</summary>

Also called: test printer, test print, printer test, printer not working. Search terms: printer, test print, printer status, diagnostics, summary, peripherals, paper roll.

</details>


---

# 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://docs.verifone.com/support-nordics/victa/how-tos/how-to-test-the-onboard-printer.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.