Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Declare and check the external tools that scenarios need

Abierto
  • ¿Algo no está bien?
#393 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
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php
Área
testing

Línea de trabajo

Start from the Behat feature files config-edit.feature and post.feature and the requirement handling described in #392. Read the test runner that filters on @require-* tags and the linter for feature files. Done means required executables are declared as tags, checked before run, and missing tools report as undeclared with the tag to add.

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

Descripción

bug scope:testing

Some scenarios depend on external tools without declaring it. For example, config-edit.feature in config-command and post.feature in entity-command use ex as the editor. Where ex is missing, these scenarios fail halfway through, after the setup has already run. In post.feature that happens at the 17th step of the scenario, after a WordPress install and 6 wp calls.

Some declared requirements are not checked at all: @require-composer, @require-download and @require-opcache-save-comments appear in feature files but never filter anything.

Steps:

  1. Support declaring required executables as tags, checked before the run like the other requirements and reported as described in #392.
  2. Check the existing @require-* tags that are currently ignored, and warn about unknown ones so that typos do not go unnoticed.
  3. When a command fails because an executable is missing, report it as an undeclared requirement, naming the tag to add, instead of as a regular test failure. This also catches tools used inside wp commands, such as mysqldump, svn or zip.
  4. Flag steps that call known external tools without the matching tag when the feature files are linted.
  5. Add the missing tags to the existing feature files in the command packages.
Lenguaje dominante
PHP
Estrellas
42
Forks
28
Merge medio
15 h 17 min
PR fusionados (30 d)
6

Preparar el entorno

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 wp-cli/wp-cli-tests

Todos los issues de wp-cli/wp-cli-tests

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.