Populate implementation report

[marcoscaceres]

Once we are in CR, and more tests get added, we will need to periodically generate an implementation report.

We can use wptreport to generate it.

[marcoscaceres]

Stub is in place. https://w3c.github.io/browser-payment-api/reports/implementation.html

Will work with @sideshowbarker to get it populated.

[marcoscaceres]

@sideshowbarker, what's the relationship between the above and the "(not very useful yet)" Dashboard: https://wptdashboard.appspot.com/payment-request

[marcoscaceres]

(Ideally, the dashboard would be the implementation report at some point, right?.... is that going to happen, or should we just populate "implementation.html" for now?)

[sideshowbarker]

what's the relationship between the above and the "(not very useful yet)" Dashboard: https://wptdashboard.appspot.com/payment-request

No relationship. They serve some of the same purposes. The dashboard is clearly better in that it is populated automatically, whereas anything we do with wptreport is manual at this point. One thing that dashboard lacks is the specialized report pages that wptreport does that show tests which are passing only in one UA (less-than-2.html) and in no UAs (complete-fails.html).

By the way the canonical URL for the dashboard is now http://wpt.fyi/

(Ideally, the dashboard would be the implementation report at some point, right?....

Yes

is that going to happen,

It is going to happen eventually but not super soon

or should we just populate "implementation.html" for now?)

Yeah in the mean time we should maintain our own report using wptreport

[marcoscaceres]

From @sideshowbarker, need to start doing:

Run:
http://web-platform.test:8000/tools/runner/index.html
Enter /payment-request under Run tests under path, then after all the
tests have run, you’ll see a Download JSON results button. Push that

And then use: https://www.npmjs.com/package/wptreport

[marcoscaceres]

Being populated manually, so closing :)