hs:manual-test

Runs session-based exploratory tests and emits anchored, gate-admissible evidence.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Dozyboy/VSF --skill hs-manual-test-dozyboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hs:manual-test
Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/skills/manual-test
Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-manual-test-dozyboy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual and exploratory testing normally produces prose claims that a quality gate cannot verify. This Skill structures manual testing as a charter → session → debrief workflow (SBTM) so every command run leaves a telemetry anchor and the result is written as a machine-readable manual check that a Definition-of-Done gate can re-read and adjudicate. ## Core Features & Use Cases - SBTM workflow: Define a one-paragraph charter, run a timeboxed session of real commands, then debrief into a structured verification check. - Anchored evidence: Arm a session via HARNESS_MANUAL_TEST_SESSION=1 or a state-dir marker so the manual_test_anchor hook records each Bash command and its output as a citable anchor. - Admissibility tiers: Evidence is classified as claimed, anchored, or anchored-plus-cosign; only an anchor plus a human co-signer distinct from the author is admissible at a hard gate. - Use Case: Before merging a change to the password-reset flow, run a 30-minute exploratory session probing expired tokens, record anchored results, get a reviewer to co-sign the charter, and attach the manual check to verification.json so the hard gate passes. ## Quick Start Ask the agent to run a manual test session with the charter "verify the password-reset flow rejects an expired token" and produce anchored evidence for the verification gate.

Frequently Asked Questions about hs:manual-test

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

FAQPage Schema
How do I run a manual exploratory test that a CI gate will accept?▼

Define a one-paragraph charter, arm the session with HARNESS_MANUAL_TEST_SESSION=1 or the state-dir marker, run real commands so the anchor hook records them, then write a manual check into verification.json citing the anchor id. For a hard gate, a reviewer distinct from the author must co-sign the charter.

What is session-based test management (SBTM) in this workflow?▼

SBTM structures exploratory testing as charter, session, and debrief. The charter states the mission and risk, the session is a timeboxed run of real probes recorded in a proof table, and the debrief emits the structured manual check consumed by the gate.

What evidence tier does a manual test need to pass a hard gate?▼

A hard gate requires anchored evidence plus a charter co-sign from a human reviewer distinct from the author. Anchored evidence alone, or a self co-sign, is admissible only at soft gates; a fabricated anchor id is rejected outright.

Does an anchored command prove the test was correct?▼

No. An anchor proves a real command ran and produced the cited output, but not that it tested the right thing. That is why hard gates also require human co-signing, and why cmd_hash and output_hash only provide transport integrity for a reviewer re-running the command.

When is the manual check required by the DoD gate?▼

The manual check is opt-in: it gates nothing unless a tier-2 policy or component explicitly declares a manual requirement. End-to-end, staging smoke, and visual export tests ride the normal JUnit-based DoD reader instead.