> For the complete documentation index, see [llms.txt](https://funtest-1.gitbook.io/funtest-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://funtest-1.gitbook.io/funtest-documentation/product-tour/test-reporting.md). # Test Reporting FunTEST also offers extensive data report and management {% embed url="" %} There 3 major types of test reports you can utilize in FunTEST 1. ### PDF or CSV Report from each test run • Create a tab called REPORT within the test file • To populate it with test results from each run refer to the test cells from the TEST tab\ • In your test sequence export the REPORT sheet as PDF

2. ### Create Test Statistics • To create a single file that includes results from each run you can utilize the STAT tab • In the STAT tab refer to cells from TEST tab that you want to record from each test run.

• This will save these values and append them to a single CSV file where you can then perform analysis such as product-to-product variant etc...\ • You can tag create test reports for overall test station statistics

Test Report monitoring resistance values from multiple tests

3. ### Upload Data to SQL Database You can also upload any test results automatically to SQL database.

{% hint style="info" %} To upload data to SQL database you need to have Database plugin. More info here [Plugin Overview](/funtest-documentation/funtest-plugins/plugin-overview.md) {% endhint %} --- # 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://funtest-1.gitbook.io/funtest-documentation/product-tour/test-reporting.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.