Doc Detective Testing FAQs

Question 1

What happens after the tests are executed?

Accepted Answer

The skill analyzes the output report, providing a detailed summary of passed and failed tests, along with descriptions of specific step failures to help you debug your documentation.

Question 2

Can I embed these tests directly into my markdown files?

Accepted Answer

Yes, the skill includes an inline test injection workflow that offers to add validated test markup directly into your source documentation for easy execution.

Question 3

What is the core rule for generating Doc Detective JSON with this skill?

Accepted Answer

The action name (such as 'goTo', 'click', or 'find') must be used as the JSON key itself. You must never use an 'action' property, as Doc Detective will reject that format.

Question 4

How does the skill ensure generated tests are valid?

Accepted Answer

The skill follows a mandatory validation gate where it saves the spec to a temporary file and runs a structural validator before any code is returned or executed.

Question 5

Does this skill prioritize text matching or CSS selectors?

Accepted Answer

It prefers text-based element location to closely match the natural language found in documentation, using selectors only when text-based matching is ambiguous or impossible.

Doc Detective Testing

Key Features

Use Cases

Doc Detective Testing

Key Features

Use Cases