Then we can programmatically query Jenkins for the builds associated with a given extension (all extensions in prod).
Purpose: To determine browser test coverage for deployed extensions.
Then we can programmatically query Jenkins for the builds associated with a given extension (all extensions in prod).
Purpose: To determine browser test coverage for deployed extensions.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | None | T437 Track state of browser tests before new wmfXX branch cut | |||
Declined | None | T456 Map operations/mediawiki-config/extension-list entries to Jenkins browser test job |
Updated description as I assume this is specifically about browser tests. Unit test job contain non-notable builds from unfinished Gerrit changes by anyone, and are also enforced to be passing before merge.
@greg Would you mind clarifying the task at hand? I am wondering what we are trying to achieve here :-]
The idea when filing this task was to have a way to track "by repository, what is the proportion that have browser tests?".