Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Add support for more test runners and linters

未关闭 适合新手
  • 哪里不对？
#3 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

@OllieinCanada 已经在做这个了。

开始于 2026年8月17日。

  • #14 来自 @OllieinCanada —— 未关闭

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
88/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
rust
领域
cli, testing-qa, tooling

调研方向

选择一个尚未勾选的 runner，先按照 CONTRIBUTING.md 中的“adding a runner”指南开始，然后检查 src/runners.rs。针对该命令更新 classify() 和 parse_outcome()，并使用真实的成功和失败输出添加测试。明确的结果能够被识别，而含糊的输出返回 Outcome::Unknown，即表示完成。

由索引模型根据 Issue 内容生成。

描述

good first issue help wanted runner

backcheck can only verify a "tests pass" claim if it recognises the command that ran. Every
runner it does not know is a session where an honest claim looks unsupported, or a fabricated
one slips through.

This is the best first contribution to the project: self-contained, immediately useful, and the
same three steps every time.

Already supported

pytest, unittest, tox, nox, cargo test, cargo nextest, go test, jest, vitest, mocha, ava,
bun test, npm/yarn/pnpm test, rspec, phpunit, dotnet test, maven, gradle, ctest, make test —
plus mypy, pyright, tsc, ruff, eslint, clippy, flake8, pylint, golangci-lint, biome.

Wanted

Pick any one and open a PR — no need to claim it first, and one runner per PR is ideal.

  • deno test
  • swift test
  • xcodebuild test / xctest
  • elixir — mix test
  • scala — sbt test
  • haskell — stack test, cabal test
  • zig build test
  • julia — Pkg.test()
  • R — testthat, devtools::test()
  • perl — prove
  • bats (bash)
  • catch2 / gtest binaries
  • k6 / playwright test / cypress run
  • terraform validate, tflint
  • shellcheck, hadolint, yamllint
  • rubocop, standardrb
  • detekt, ktlint, spotless

How

All of it lives in src/runners.rs. See
CONTRIBUTING.md for the full walkthrough.

  1. Recognise the command in classify() — return the CheckKind and a short runner name.
  2. Read its outcome in parse_outcome() — pull pass/fail out of the summary line.
  3. Add a test with real passing and failing output, copied from an actual run.

The one rule

Return Outcome::Unknown when the output does not clearly say. A wrong "verified" is far more
damaging than an honest "could not tell" — backcheck is only worth installing if its
"supported" verdicts mean something.

主要语言
Rust
星标
1
派生
2
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

VectorInstitute/backcheck 的其他 Issue

查看 VectorInstitute/backcheck 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。