WordPress/phpunit-test-runner

Document what a test runner should do when a test fails

Open

#50 opened on Oct 11, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)PHP (75 forks)github user discovery
documentationhelp wantedtooling

Repository metrics

Stars
 (76 stars)
PR merge metrics
 (Avg merge 5d 16h) (1 merged PR in 30d)

Description

When a test runner executes the tests for the first time, they may find one or more failures. We should document what they should do in this case.

Contributor guide

Research direction
Review existing PHPUnit documentation and common conventions for handling test failures. Look at similar WordPress test runner issues to see how behavior is documented.
Tech stack
php
Domain
testing
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
95