web-platform-tests/wpt

https status of tests computed by runner and not in manifest

Open

#12,379 opened on Aug 9, 2018

View on GitHub
 (7 comments) (0 reactions) (0 assignees)HTML (4,581 stars) (2,898 forks)batch import
good first issueinframanifestpriority:backlog

Description

For the same reason as #11285, we should move this into the manifest to avoid having logic in every runner.

Contributor guide

Tech stack
pythonhtmlcssjavascript
Domain
testinginfrastructure
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Understanding of wpt manifestFamiliarity with issue #11285Knowledge of test runner architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Refer to issue #11285 for context on the analogous change. Examine the manifest schema and runner implementations in the wpt repository to identify where HTTP status is currently computed and where it should be moved. Look for duplicated logic across runners to consolidate into the manifest.