doc-testing

Name: doc-testing
Availability: InStock
Author: Doc Detective

Convert documentation into Doc Detective test specifications for browser testing.

13|3|Updated Jan 21, 2026

Search Tags:#automation #documentation #validation #browser-testing #doc-detective #test-spec #doc-testing

Ready to run

npx skills add https://github.com/doc-detective/agent-tools --skill doc-testing-doc-detective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-testing
Source: https://github.com/doc-detective/agent-tools/tree/main/plugins/doc-detective/skills/doc-testing
Command: npx skills add https://github.com/doc-detective/agent-tools --skill doc-testing-doc-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires doc-detective-common, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the transformation of documentation into Doc Detective test specifications and provides a framework to validate that documented procedures align with actual UI behavior.

Core Features & Use Cases

Text-to-spec conversion: Map documented steps (goTo, click, find, type) into Doc Detective actions to produce executable test specs.
Validation & integrity: Validate generated specs using the built-in validator and optionally use schema validation when available.
Injection & execution readiness: Offer inline test injection into source docs and execute tests against web UIs with Doc Detective.
Use Case: Convert a step-by-step getting started guide into a test spec and verify it against a staging environment.

Quick Start

Provide a documentation file, generate a Doc Detective test spec, run the validator, and optionally inject or execute the test.

Frequently Asked Questions about doc-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert documentation into executable test specs?▼

You can convert documentation into executable test specs by mapping documented steps into Doc Detective actions like goTo, click, find, and type to produce an automated test specification.

What is automated browser testing for documentation validation?▼

Automated documentation validation transforms written guides into executable test specs and runs them against web UIs to verify that documented procedures align with actual application behavior.

Do I need a Node.js environment to run doc-detective test specs?▼

Yes, a Node.js environment is required to execute Doc Detective test specifications. You also optionally use doc-detective-common to provide schema validation for the generated tests.

Can I inject inline tests directly into source documentation?▼

Yes, you can inject inline tests directly into source documentation. The framework supports inline test injection to embed executable validation steps within your existing docs.

What is the best way to validate a getting started guide against a staging environment?▼

The best way to validate a getting started guide is to generate a Doc Detective test spec from the steps and execute it against your staging environment to verify actual UI behavior.

How do I validate generated test specs for integrity before execution?▼

You validate generated test specs for integrity using the built-in validator, optionally leveraging schema validation from doc-detective-common to ensure test specification accuracy before execution.