> For the complete documentation index, see [llms.txt](https://docs.fieldcommgroup.org/dd-stat-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldcommgroup.org/dd-stat-documentation/help/manual-testing.md).
# Manual Testing
Some of the test cases in the test specification are not automated. For some, it is not possible to automate the test case. In others, automation will be added to DD-STAT in future releases.
These test cases must be run manually by the test engineer. This section describes how the automation interoperates with the engineer.
**Detail.log file and report summary (HTML)**
In the detail.log, manual test cases will be marked with \[WARN] logging level. The warning will also show in the graphical report summary. Also, the End: statement will contain the text "manual".
```log
[WARN] - Unknown: TFP711_013 is evaluated manually.
[INFO] - End: TFP711_013 manual Unknown (Warning)
```
**Test report document**
In this Word document, each section of tests contains a table summarizing the pass/fail results. In the automated tests, the disposition column is set by the automation and is overwritten each time the automation runs. In the manual cases, this cell will not be overwritten. This allows the test engineer to manually type the test result into these cells, and the values are preserved from run to run. When you first open the report, these cells will be empty.
In the detailed section for each test case, the result will show as Unknown and the evaluation as Manual. Text which is written directly into the document **under** the boxed automation results will not be overwritten from run to run.
---
# 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://docs.fieldcommgroup.org/dd-stat-documentation/help/manual-testing.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.