Epic: Explicit test requirements

Open
#395 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
cli, php
Domain
testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
PHP
Stars
42
Forks
28
Avg merge
17h 14m
Merged PRs (30d)
11

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wp-cli/wp-cli-tests

All issues in wp-cli/wp-cli-tests

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.