Epic: Explicit test requirements

未关闭
#395 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
cli, php
领域
testing

调研方向

No files or tests are named in this epic. Start by reading the framework's scenario loading and CI scripts to see where environment checks happen. Done means scenarios needing missing extensions or tools are either filtered with a clear report or stop the run before starting.

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

描述

scope:testing

Scenarios that need something the environment does not provide, such as a PHP extension, a database type or an external tool, should never cost a run and never disappear unnoticed.

They should either be filtered out up front with a clear report of what was not tested and why, or stop the run before it starts when the environment is expected to be complete, as on CI. A scenario failing halfway through because a tool is missing wastes compute and hides the actual cause.

主要语言
PHP
星标
42
派生
28
平均合并
18 小时 52 分钟
30 天内合并 PR
27

环境准备

从这里开始

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

wp-cli/wp-cli-tests 的其他 Issue

查看 wp-cli/wp-cli-tests 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

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