Declare and check the external tools that scenarios need
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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:
- Support declaring required executables as tags, checked before the run like the other requirements and reported as described in #392.
- Check the existing
@require-*tags that are currently ignored, and warn about unknown ones so that typos do not go unnoticed. - 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
wpcommands, such asmysqldump,svnorzip. - Flag steps that call known external tools without the matching tag when the feature files are linted.
- Add the missing tags to the existing feature files in the command packages.
- 主要語言
- PHP
- 星號
- 42
- 分支
- 28
- 平均合併
- 18 小時 52 分鐘
- 30 天內合併 PR
- 27
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
wp-cli/wp-cli-tests 的其他 Issue
-
scope:testing status:unconfirmed
難度 2/5 1-3 小時 新手友好度 65/100
wp-cli/wp-cli-tests#389 · 1 則留言 ·
維護者通常 1 天內回覆
-
scope:testing
難度 4/5 3-5 天 新手友好度 25/100
wp-cli/wp-cli-tests#427 ·
維護者通常 1 天內回覆
-
scope:testing
難度 4/5 3-5 天 新手友好度 22/100
wp-cli/wp-cli-tests#426 ·
維護者通常 1 天內回覆
-
scope:testing
難度 4/5 3-5 天 新手友好度 25/100
wp-cli/wp-cli-tests#425 ·
維護者通常 1 天內回覆
-
scope:testing
難度 5/5 一週以上 新手友好度 20/100
wp-cli/wp-cli-tests#395 ·
維護者通常 1 天內回覆
查看 wp-cli/wp-cli-tests 的全部 Issue
相似的 Issue
-
mobile-app
難度 2/5 1-3 小時 新手友好度 74/100
Open-Locker/Open-Locker#352 ·
維護者通常 1 天內回覆
-
[Bug]: SCIM Users groups[].value is returned as an integer, causing authentik user discovery to fail未關閉
難度 2/5 1-3 小時 新手友好度 62/100
grokability/snipe-it#20006 ·
維護者通常 1 天內回覆
-
fixed
難度 2/5 1-3 小時 新手友好度 62/100
firefly-iii/firefly-iii#13150 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
TYPO3-Solr/ext-solr#4828 ·
維護者通常 5 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 3 天內回覆