> 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/what-is-funtest.md). # What is FunTest? FunTEST is a text executive that allows you to manage and create automated test sequences for hardware testing. Our goal is to **simplify the development and maintenance of hardware testing**. With FunTEST you can **automate your testing without writing any code**. No more the tedious process of developing software from scratch to execute your testing. With FunTEST you can: * **Control your hardware** through FunTEST open plugin architecture * **Create test sequences** in a spreadsheet format * Monitor testing through **built-in Operator Interface** * Export and Manage your **Test Data** ## **Video Overview** {% embed url="" %} ### FunTest Block Diagram
### ### Learn more

Product Tour		Discover main featuresNavigationfunTEST_logo_hires_4k_logo.png

Creating Test Sequence		Learn how to create test sequence in funTEST2023-10-18_10h33_33.png
How To'sLearn how to use funTEST through short video tutorialsHow To's2023-10-27_14h23_33.png
--- # 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/what-is-funtest.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.