WordPress/phpunit-test-runner

Research and document slow/risky tests

Open

#51 opened on Oct 11, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)PHP (75 forks)github user discovery
help wantedresearch

Repository metrics

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

Description

danielbachhuber [10:17 AM] I'd like to spend a little bit of time looking at the "slow" and "risky" tests to see if we can do anything about them [10:18] to someone not intimately involved with core development, slow/risky tests seem like an issue with the environment, not core

Contributor guide

Research direction
Identify slow and risky tests in the WordPress PHPUnit test runner by analyzing test execution times and flakiness, then document findings for future improvements.
Tech stack
php
Domain
testing
Issue type
Research
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.
1-3 hours
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
PHPTesting concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85