# DD Standard Test Automation Tool

The requirements for submitting an DD for registration are described in FieldComm Group [support](https://support.fieldcommgroup.org/en/support/solutions/articles/8000018143-hart-edd-registration).

The DD Standard Test Automation Tool (DD-STAT) is a comprehensive test automation tool which assists members of FieldComm Group with the process of registering HART DD projects.&#x20;

### Key features

* **Collection** It assists users to correctly assemble required source code and documentation for the submission.
* **Evaluation** It examines DD source code and tokenizer outputs, comparing them to the requirements of the DD test specification.
* **Reporting** It places the results of the examination into a test report template simplifying the reporting process.
* **Submission** It bundles the information that is required for registration and copies it to FieldComm Group servers.

### DD-STAT tests fall into three categories:

* **Automated** tests evaluate DD source code and other artifacts
* **Tokenizer** tests inspect specific outputs from the tokenizers
* **Manual** tests rely on a test engineer to inspect the code base and provide a conclusion

The tool is configured as an extension to the Visual Studio Code ( VSCode ) editor in two pieces:

* A command line interface that could be run from a Windows terminal or in a DevOps pipeline.
* A user interface window that runs inside the VSCode IDE, which eases user interaction with the tool.


---

# Agent Instructions: 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:

```
GET https://docs.fieldcommgroup.org/dd-stat-documentation/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
