Development & Runtime

dsh-flakefinder

STARDUSTLC666/dsh-flakefinder · ★ 1

STARDUSTLC666Curated

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

License
MIT
Added
2026-08-17
Maintenance
active
Install kind
github
npm
dsh-flakefinder
Manifest details
Manifest status
Declared
Manifest path
package.json#dsh
Manifest checked
2026-08-19
Lifecycle scripts
None found

Static manifest checks report declarations only; they are not compatibility or security review.

安装

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

GitHub 源码安装:首次需按提示配置 allowBuilds 构建授权后重试

For install and environment setup, plus plugin development tutorials, see DSH community docs ↗

README

Source README · body: en · Read Chinese README

Table of contents
  1. FlakeFinder
  2. Features
  3. Install
  4. Start using it
  5. Before you start
  6. Plugin updates
  7. Documentation
  8. Feedback and contributions
  9. License

简体中文 · English

FlakeFinder

Turn intermittent test failures into traceable evidence.

npm 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.1-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