DeepSeek Harness Plugin

STARDUSTLC666/dsh-flakefinder

Stars ★ 1 Downloads (30d) 5,041 Category Development & Runtime Added 2026-08-17 npm dsh-flakefinder

Test-stability tools: repeatedly run vitest/jest/pytest/node:test suites, classify flaky cases, keep history, maintain a quarantine manifest and health self-check.

Install

# from npm (prebuilt)

dsh plugin --profile web add dsh-flakefinder

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:STARDUSTLC666/dsh-flakefinder

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

简体中文 · English

FlakeFinder

Turn intermittent test failures into traceable evidence.

downloads total downloads

Install · Workflow · Full guide

Features

  • Investigate Vitest, Jest, pytest and node:test runs.
  • Keep each run’s outcome and failure history.
  • Narrow the cause using differences and maintain quarantine lists.

Install

Open Plugins in the DSH desktop app and install dsh-flakefinder. If the CLI is available:

dsh plugin --profile desktop add dsh-flakefinder

For the web profile, replace desktop with web. Restart that DSH profile after installation. The package’s DSH requirement is >=0.2.2-rc.3.

Start using it

  1. Start in the target test repository and confirm dependencies and the test command work.
  2. Provide the command, repeat count and scope; review the execution plan and expected file changes first.
  3. Run after confirmation and inspect per-run results, failure logs and the workspace isolation inventory.
  4. Use reproducible differences to narrow the cause; rerun the same command after fixing it, and retain an unreproduced result when appropriate.

Example request:

Explain the plan and effects of repeating this test command, then run it after confirmation and retain every result.

Before you start

Repeated tests execute real project commands. Failure to reproduce is not proof that a flaky issue is absent.

Configuration, detailed tools and troubleshooting: full reference.

Plugin updates

Check updates at the bottom of the workbench or native plugin details. Automatic checks are on by default; automatic installation is off. You choose whether to install and when to restart. Suite-managed components update with their bundle. Update behavior.

Documentation

Feedback and contributions

If the plugin helps, a Star makes it easier for others to discover. Report problems or suggest improvements in Issues; code and documentation PRs are welcome. Include versions and reproduction steps, and remove credentials from reports.

License

MIT

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.