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

Abierto
  • ¿Algo no está bien?
#275 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, shell
Área
testing-qa, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Python
Estrellas
4
Forks
1
Merge medio
10 h 41 min
PR fusionados (30 d)
79

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cpp-best-practices/project_validator

Todos los issues de cpp-best-practices/project_validator

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.