> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/freemium/installation-guide/test-case.md).
# Test case
Run a test case to check that SMTP and app is configures correctly.
First, setup 1 customer to test with according the the '[Customers](/freemium/user-guide/customers.md)' section in the 'User Guide'.
{% hint style="danger" %}
**IMPORTANT** - To be able to run this test you need a Sales Invoice that we will later 'Post'. If your using a real invoice for the test, put yourself as the email receiver first to confirm it works.
{% endhint %}
* In Business Central, search and go to the page "Sales Invoices"
* Open the sales invoice that you want to run the test with.
* Under the "Invoice Details" section, you will find the field 'GEDI Profile'. Change this to 'PDF-BC', in order to activate the functionality.
* 'Post' the invoice.
* If you search and go to the page 'Posted Sales Invoice' you can find a column with 'GEDI Status' - this should now have status 'Requested'.
* Search and go to the page 'GEDI Message Queue'.
* Here you will find a row with your invoice number in 'Message ID' column and with the 'Message Code' = 'SINV-81-MR', probably it's the last row in the list.
* Mark the row, and go to 'Home' tab and click 'Run Message' to manually trigger the invoice.
* If you go back to 'Posted Sales Invoices' you can see that the GEDI Status is now 'Sent'
{% hint style="success" %}
If you received the e-mail this means the test was successful and SMTP and customer configuration is correct.
{% endhint %}
{% hint style="warning" %}
If you changed the customer email to your own address for the test, don't forget to set it back to the correct customer email!
{% endhint %}
During this test you manually processed the message via our 'GEDI Message Queue', in the next step we will create and schedule 'Job Queue Entries' to handle this for us automatically in the background.
---
# 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.goldenedi.com/freemium/installation-guide/test-case.md?ask=&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.
