> For the complete documentation index, see [llms.txt](https://guides.kenst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.kenst.com/test-design/functional.md). # Functional Testing The goal of functional testing is to focus on individual functions, testing them one by one. Often this goal is difficult to achieve on it's own. Possible Strategy: 1. Create a function list (an outline of functions in the app or in the release) * Initial function list can be an outline * Becomes more fully-detailed over time (if this is your primary technique) 2. Do this testing first before attempting more complex tests that involve several functions, might find blockers --- # 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://guides.kenst.com/test-design/functional.md?ask=&goal= ``` `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.