Output Formats

Use the -f / --output-format option to control which file format testdoc generates.
The flag is compatible with all other options (tag filters, source prefix, title, …).

Value	Description
html	Interactive HTML page (default)
json	Machine-readable JSON of the full suite tree

---

HTML (default)

HTML is the default and requires no explicit flag.

testdoc tests/ TestDocumentation.html
# equivalent:
testdoc -f html tests/ TestDocumentation.html

See the Jinja2 page for details about customising the HTML template.

---

JSON

The JSON output serialises the complete parsed suite tree — the very same data model that is also used by the MkDocs renderer — into a single .json file.
This makes the output easy to consume in dashboards, CI quality gates, or any custom tooling without having to parse Robot Framework files yourself.

testdoc -f json tests/ TestDocumentation.json

Example output structure:

{
  "id": "s1",
  "name": "Testcases",
  "is_folder": true,
  "source": "/path/to/tests",
  "metadata": null,
  "type": "directory",
  "doc": null,
  "test_count": 17,
  "tests": [],
  "suites": [
    {
      "name": "Component A",
      "tests": [ ... ],
      ...
    }
  ],
  "user_keywords": []
}

You can also set output_format = "json" in your TOML configuration file:

[tool.testdoc]
output_format = "json"

---

Combining with other options

The output format flag works with the full set of testdoc options:

# JSON with tag filter and custom title
testdoc -f json -t "Nightly Suite" -i Regression tests/ nightly.json

# JSON with source prefix
testdoc -f json -s "github::https://github.com/myorg/myrepo" tests/ docs.json