Shell: urchin tests (suffix-less files under test/), .zsh-theme scripts and .zunit tests, bash versions as a toolchain axis

オープン
  • 何か問題がありますか？
#275 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python, shell
領域
testing-qa, tooling

調査の方向性

Start with the Shell ecosystem profile in docs/ecosystems/shell.md, which says platform-matrix is not judged, and with the .map.json unrecognised_suffixes handling that produces the "no tests found" message. Three separate detection gaps are raised: urchin tests under test/, .zsh-theme and .zunit files, and bash versions as a platform axis. Done means the three audit cases in corpus/projects.toml produce the expected results, and the ohmyzsh repro in the issue no longer reports "no tests found" for .zunit files.

索引モデルが issue の本文から書いたものです。

説明

nvm's 300+ tests are urchin tests (suffix-less shell files under test/fast, test/slow, …) run by every workflow → "no tests found". ohmyzsh's 144 .zsh-theme files are zsh scripts and plugins/dotenv/tests/*.zunit are zunit tests (not run in CI, so the FAIL stands but "no tests found" is wrong). bats-core tests 11 bash versions across linux/macos/windows/freebsd/alpine; Shell has no platform axis and the project is judged as Python "0 OS".

Evidence from the corpus audit

nvm-sh/nvm / tests-run
  • kind: UNSUPPORTED
  • actual: [FAIL] tests-run: JavaScript/TypeScript: no tests found (...); Shell: no tests found (bats tests (*.bats), shellspec specs (spec/*_spec.sh) or shunit2 tests (*_test.sh))
  • expected: nvm's 300+ tests are urchin tests (suffix-less shell files under test/fast, test/slow, ...), run by every test workflow.
  • evidence: Makefile:6: URCHIN := urchin; package.json scripts: "test": "shell=$(basename -- ...); make test-$shell"; test/fast/, test/slow/, test/sourcing/ directories.
  • repro: unclear (urchin has no file suffix convention; it runs every executable under a directory).
  • confidence: medium
ohmyzsh/ohmyzsh / detection, tests-run
  • kind: UNSUPPORTED
  • actual: .map.json unrecognised_suffixes: .zsh-theme x144, .zunit x3; Shell: no tests found
  • expected: .zsh-theme files are zsh scripts (Shell); plugins/dotenv/tests/*.zunit are zunit tests (CI does not run them, so the FAIL stands, but the message "no tests found" is wrong).
  • evidence: themes/*.zsh-theme (144 files); plugins/dotenv/tests/basic-parsing.zunit, security.zunit, compatibility.zunit; .github/workflows/main.yml:36: zsh -n "$file" || return 1 (syntax check only).
  • repro: a tests/a.zunit file.
  • confidence: low
bats-core/bats-core / platform-matrix, tests-run (docs)
  • kind: UNSUPPORTED
  • actual: [SKIP]-equivalent for Shell platform-matrix (judged only as Python: CI covers 0 OS(es)); Documentation site: tests found in 1 file(s), but no CI configuration runs sphinx-build -W docs docs/_build
  • expected: bash versions are a real toolchain axis here (11 versions x linux/macos/windows/freebsd/alpine); the docs are built by Read the Docs.
  • evidence: .github/workflows/tests.yml:199-202: bash-version: / version: ['3.2', '4.0', '4.1', '4.2', '4.3', '4.4', '4', '5.0', '5.1', '5', 'rc']; .readthedocs.yml:3-4: sphinx: / configuration: docs/source/conf.py.
    docs/ecosystems/shell.md says platform-matrix is not judged because "shells have none CI names" - this project names them.
  • repro: unclear
  • confidence: low

Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

主要言語
Python
スター
4
フォーク
1
平均マージ
10時間 41分
マージ済み PR（30日）
79

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

cpp-best-practices/project_validator のほかの issue

cpp-best-practices/project_validator の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。