Inline Test Injection FAQs

Name: Inline Test Injection
Author: doc-detective

Question 1

What file types does Inline Test Injection support?

Accepted Answer

The skill supports a wide range of documentation formats including Markdown (.md), MDX (.mdx), HTML, XML/DITA, and AsciiDoc (.adoc).

Question 2

Does it handle custom markup or configurations?

Accepted Answer

Yes, if a .doc-detective.json or .doc-detective.yaml file exists in your project, the skill will load and respect your custom markup patterns.

Question 3

How does it know where to place the test steps in the document?

Accepted Answer

It uses a semantic matching engine that scores the similarity between test actions (like 'click' or 'type') and document elements (like links or bold text) to place comments exactly where they belong.

Question 4

What happens if a test step doesn't match any text in my doc?

Accepted Answer

Steps that cannot be matched semantically are flagged as 'unmatched' in the preview and are typically placed at the end of the document for manual placement.

Question 5

Can I see the changes before my files are modified?

Accepted Answer

Yes, the skill includes a preview mode that generates a diff of the planned injections so you can review accuracy before applying the changes.

Inline Test Injection

Key Features

Use Cases

Inline Test Injection

Key Features

Use Cases