Closed Bug 1548289 Opened 7 months ago Closed 5 months ago

Dashboard tracking progress towards Puppeteeer

Categories

(Remote Protocol :: Agent, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ato, Assigned: ato)

Details

A dashboard that tracks our progress towards puppeteer and
puppeteer-mvp would be a useful tool for communicating and
visualising our continued progress.

Some notes and ideas:

  • Which Puppeteer APIs are supported

    It’s hard to tell what events, specifically, a Puppeteer API
    causes. Requires manual survey of the Puppeteer code. Also
    doesn’t tell us if we’re actually conformant beyond the fact
    that it’s there in the protocol.

  • Which CDP methods and events are implemented/partially
    implemented/not implemented

    Link to individual bugs? Should take into account depedency
    tree for partial implemented status, perhaps a percentage rate?

  • Puppeteer test suite pass rate over time and overview of
    currently passing and failing tests

    Extract data from TaskCluster.

  • Bugzilla burndown rate over time towards puppeteer-mvp

    Must include dependency tree. Nothing irrelevant must block
    this bug, otherwise the numbers will be skewed.

  • Bugzilla burndown rate overall for Remote Protocol :: *

Assignee: nobody → ato
Status: NEW → ASSIGNED
Priority: -- → P1

I have done a (not so useful) prototype, but moving this to the
backburner because a drill-down towards
https://bugzilla.mozilla.org/show_bug.cgi?id=puppeteer-mvp would
be of much more immediate use.

Status: ASSIGNED → NEW
Priority: P1 → P2

I pushed the work I did to http://github.com/andreastt/remotedash,
but as I said in my previous comment, we shouldn’t publicise this
until we have data tracking puppeteer-mvp specifically.

Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.