perrylink/dsh-test-drive
Isolated installation and smoke test driver: package the warehouse or npm into a one-time DSH_HOME configuration, verify the bundle patch layer and startup log, output a structured pass/fail matrix (JSON/Markdown) for consumption by the scoring pipeline, and isolate and clean up all its own temporary directories; npm dsh-test-drive 0.2.3
Isolated install-and-smoke test drives for DSH plugins, run in a throwaway profile so your real ~/.dsh stays untouched. One test_drive call takes a target through the complete pipeline: dsh plugin add, a --dump-config patch check, a headless boot smoke test (FAILED-marker scan plus an optional one-shot task), then cleanup. Every record carries the discriminator schema "dsh-test-drive/v1" with first-class stage fields such as stages.install.status and stages.smoke.status. Temp directories are created under a dedicated dsh-test-drive- prefix and tracked in a live ownership registry, so only this plugin's own directories are ever removed.
Install
dsh plugin --profile web add dsh-test-drivenpm package dsh-test-drive 0.3.11 (registry-verified 2026-09-10; registry repository field -> github.com/PerryLink/dsh-test-drive). The README also documents a git form (github:PerryLink/dsh-test-drive#<commit-sha>) which needs an allowBuilds entry for the prepare build; prebuilt npm packages need no allowance. Restart the profile, then use test_drive or /testdrive. Uninstall: dsh plugin --profile web remove dsh-test-drive.
Compatibility
DeepSeek Harness dsh-v0.1.5-rc.1 (README verified 2026-09-10; npm dependency lines 0.1.2-rc.1 and 0.1.5-rc.1 as peer deps). Requires the dsh CLI and pnpm on PATH.
Details
- Repo: perrylink/dsh-test-drive
- Category: Coding & Development
- Stars: 3
- Version: npm dsh-test-drive 0.3.11 (registry-verified 2026-09-10)
- Last push: 2026-09-03
- First seen: 2026-08-17
FAQ
- How do I install dsh-test-drive?
- Run: dsh plugin --profile web add dsh-test-drive (npm channel, prebuilt), restart the profile, then call test_drive or /testdrive from a session.
- Will a test drive touch my real DSH setup?
- No. Each drive runs in a throwaway profile, and temp directories are created only under a dsh-test-drive- prefix and tracked in an ownership registry so nothing else is removed.
- What does a test drive actually run?
- It installs the target, checks the --dump-config patch, boots the profile headlessly scanning for FAILED markers (with an optional one-shot task), and reports each stage — for example stages.install.status and stages.smoke.status.
Alternatives
nexu-io/open-design · titanwings/colleague-skill · dsh-market/dsh-market