WebDriver/RemoteProtocol/Meetings/2019/12/13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "… on St Nicolaus day! 🎅🏻 == Agenda == * Actions ** Update the 2020 planning document based on priorities set out in this meeting (''ato'') ** File bug about running...")
 
m (Whimboo moved page Remote/Meetings/2019/12/13 to WebDriver/RemoteProtocol/Meetings/2019/12/13: Reorganization for WebDriver BiDi project documenation)
 
(11 intermediate revisions by 4 users not shown)
Line 1: Line 1:
… on St Nicolaus day! 🎅🏻
… on the unlucky Friday!


== Agenda ==
== Agenda ==
Line 5: Line 5:
* Actions
* Actions
** Update the 2020 planning document based on priorities set out in this meeting (''ato'')
** Update the 2020 planning document based on priorities set out in this meeting (''ato'')
** File bug about running Puppeteer unit tests with Fission enabled (''ato'')
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1603078 File bug about running Puppeteer unit tests with Fission enabled] (''ato'')
* Close out the Alpha Project (''mmucci'')
* Review forecast and select MVP for Beta Project (''mmucci'')
** <strike>Review Q1 2020 planning document</strike>
** <strike>Triage remaining APIs to assess whether they are blocked by Fission</strike>


== Roster ==
== Roster ==


; Present
; Present
mmucci, whimboo, ato, maja_zf, digitarald
; Regrets
; Regrets
AutomatedTester


== Minutes ==
== Minutes ==
=== Close out the Alpha project ===
https://docs.google.com/spreadsheets/d/169Wvq_NGcUJjPDeX_xPjffs6__tIlQDtKyemqlor3QI/edit?usp=sharing
* 100% of the backlog completed
* We exceed our original forecast
=== Preparing for Beta ===
* mmucci asked for input about list of bugs to include in Beta.
** Think about what you definitely ''don't'' want in Beta.
** The team added a few bugs. Notably Fission work and schema validation were missing.
* How much contingency do we want?
** Example: 100% (one contingency bug for each bug in the backlog) gets us to a July 2020 completion date.
** How much uncertainty do we feel? Are there particular (meta) bugs that might generate a lot of new bugs to work on?
** Can we estimate future contingency based on the number of new bugs we've filed in the past couple of months? For example, [https://bugzilla.mozilla.org/buglist.cgi?priority=P1&priority=P2&list_id=15032922&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=2019-11-15&product=Remote%20Protocol 19 P1 bugs] have been ''filed'' since mid-November.
mmucci to confirm with AutomatedTester later today.
==== Proposed measurable goals ====
Other ways to measure our progress? Are there intermediate goals we can aim for?
# Pass 1 gutenberg test: to account for getting their extensive test setup to work
# Support a subset of Puppeteer examples
# Support a subset of Puppeteer unit tests (e.g. exclude the tests that represent regressions and edge cases).
# Support one or two other specialized tools, e.g. pdf generation
; digitarald
: Cross-browser support doesn't necessarily impact all Puppeteer use-cases: for example, a specific tool like a PDF generator doesn't need to use Firefox unless there's a performance advantage.
== Actions ==
* Review Q1 2020 planning document?
* Triage remaining APIs to assess whether they are blocked by Fission (whimboo, ato)


== Recording ==
== Recording ==
None.


== [[Remote/Milestones#Alpha|Status of Milestone 1]] ==
== [[Remote/Milestones#Alpha|Status of Milestone 1]] ==


* '''Last week:''' 78 Total; 48 Open (61.54%); 30 Resolved (38.46%); 0 Verified (0%);
* '''Last week:''' 78 Total; 48 Open (61.54%); 30 Resolved (38.46%); 0 Verified (0%);
* '''This week:''' 80 Total; 47 Open (58.75%); 33 Resolved (41.25%); 0 Verified (0%);


== Changelog ==
== Changelog ==


<pre>
<pre>
a4ccc3553ab0    Henrik Skupin  Bug 1588622 - [remote] Implement "layoutViewport" and "contentSize" for Page.getLayoutMetrics. r=remote-protocol-reviewers,maja_zf
e945aae1d389    Maja Frydrychowicz      Bug 1597879 - Implement Page.addScriptToEvaluateOnNewDocument; r=remote-protocol-reviewers,whimboo,ato
a53e45846665    shindli Backed out 9 changesets (bug 1596918) for causing mochitest permafailures in toolkit/content/tests/chrome/test_findbar_events.xhtml CLOSED TREE
304fa3fed99f    Kris Maglione  Bug 1596918: Part 3b - Run code formatters on files changed by previous patch. r=mccr8,remote-protocol-reviewers,ato
8e14c4aeea49    Kris Maglione  Bug 1596918: Part 3a - Scripted rewrite of most ContentTask.spawn calls to SpecialPowers.spawn calls. r=mccr8,remote-protocol-reviewers,ato
a86046465cd4    Maja Frydrychowicz      Bug 1597877 - Implement Page.createIsolatedWorld; r=remote-protocol-reviewers,whimboo,ato
b33ca346dd08    Maja Frydrychowicz      Bug 1597877 - Make Runtime.enable/disable control notifications only; r=remote-protocol-reviewers,whimboo,ato
b25ef4bd85a8    Maja Frydrychowicz      Bug 1597877 - Allow many ExecutionContexts per inner window; r=remote-protocol-reviewers,ato,whimboo
70a53dbdd4b7    Maja Frydrychowicz      Bug 1597877 - Identify internal methods in Runtime domain; r=remote-protocol-reviewers,whimboo
9ef2f2fbf2f2    Maja Frydrychowicz      Bug 1597877 - Report name, origin, type in Runtime.executionContextCreated; r=remote-protocol-reviewers,ato,whimboo
ce88fdca1fea    Maja Frydrychowicz      Bug 1597877 - Make frameId a string; r=remote-protocol-reviewers,ato,whimboo
00c691f11046    Noemi Erli      Backed out 9 changesets (bug 1596918) for causing multiple browser-chrome failures
b65a53a83b48    Kris Maglione  Bug 1596918: Part 3b - Run code formatters on files changed by previous patch. r=mccr8,remote-protocol-reviewers,ato
6e89cdf9c855    Kris Maglione  Bug 1596918: Part 3a - Scripted rewrite of most ContentTask.spawn calls to SpecialPowers.spawn calls. r=mccr8,remote-protocol-reviewers,ato
444cc56888cc    Daniel Varga    Backed out 17 changesets (bug 1596918) for multiple browser-chrome and dev-tools failures. On a CLOSED TREE
7c49f5cd9b3b    Kris Maglione  Bug 1596918: Part 3b - Run code formatters on files changed by previous patch. r=mccr8,remote-protocol-reviewers,ato
799653ebd029    Kris Maglione  Bug 1596918: Part 3a - Scripted rewrite of most ContentTask.spawn calls to SpecialPowers.spawn calls. r=mccr8,remote-protocol-reviewers,ato
</pre>
</pre>


Line 41: Line 107:


== PTO (🎄) ==
== PTO (🎄) ==
* maja_zf: Dec 23rd to Jan 9th or 10th
* ato:
** Tuesday 17th December
** Monday 23rd December to Friday 3rd January 2020

Latest revision as of 20:09, 26 February 2021

… on the unlucky Friday!

Agenda

  • Actions
  • Close out the Alpha Project (mmucci)
  • Review forecast and select MVP for Beta Project (mmucci)
    • Review Q1 2020 planning document
    • Triage remaining APIs to assess whether they are blocked by Fission

Roster

Present

mmucci, whimboo, ato, maja_zf, digitarald

Regrets

AutomatedTester

Minutes

Close out the Alpha project

https://docs.google.com/spreadsheets/d/169Wvq_NGcUJjPDeX_xPjffs6__tIlQDtKyemqlor3QI/edit?usp=sharing

  • 100% of the backlog completed
  • We exceed our original forecast

Preparing for Beta

  • mmucci asked for input about list of bugs to include in Beta.
    • Think about what you definitely don't want in Beta.
    • The team added a few bugs. Notably Fission work and schema validation were missing.
  • How much contingency do we want?
    • Example: 100% (one contingency bug for each bug in the backlog) gets us to a July 2020 completion date.
    • How much uncertainty do we feel? Are there particular (meta) bugs that might generate a lot of new bugs to work on?
    • Can we estimate future contingency based on the number of new bugs we've filed in the past couple of months? For example, 19 P1 bugs have been filed since mid-November.

mmucci to confirm with AutomatedTester later today.

Proposed measurable goals

Other ways to measure our progress? Are there intermediate goals we can aim for?

  1. Pass 1 gutenberg test: to account for getting their extensive test setup to work
  2. Support a subset of Puppeteer examples
  3. Support a subset of Puppeteer unit tests (e.g. exclude the tests that represent regressions and edge cases).
  4. Support one or two other specialized tools, e.g. pdf generation
digitarald
Cross-browser support doesn't necessarily impact all Puppeteer use-cases: for example, a specific tool like a PDF generator doesn't need to use Firefox unless there's a performance advantage.

Actions

  • Review Q1 2020 planning document?
  • Triage remaining APIs to assess whether they are blocked by Fission (whimboo, ato)

Recording

None.

Status of Milestone 1

  • Last week: 78 Total; 48 Open (61.54%); 30 Resolved (38.46%); 0 Verified (0%);
  • This week: 80 Total; 47 Open (58.75%); 33 Resolved (41.25%); 0 Verified (0%);

Changelog

a4ccc3553ab0    Henrik Skupin   Bug 1588622 - [remote] Implement "layoutViewport" and "contentSize" for Page.getLayoutMetrics. r=remote-protocol-reviewers,maja_zf
e945aae1d389    Maja Frydrychowicz      Bug 1597879 - Implement Page.addScriptToEvaluateOnNewDocument; r=remote-protocol-reviewers,whimboo,ato
a53e45846665    shindli Backed out 9 changesets (bug 1596918) for causing mochitest permafailures in toolkit/content/tests/chrome/test_findbar_events.xhtml CLOSED TREE
304fa3fed99f    Kris Maglione   Bug 1596918: Part 3b - Run code formatters on files changed by previous patch. r=mccr8,remote-protocol-reviewers,ato
8e14c4aeea49    Kris Maglione   Bug 1596918: Part 3a - Scripted rewrite of most ContentTask.spawn calls to SpecialPowers.spawn calls. r=mccr8,remote-protocol-reviewers,ato
a86046465cd4    Maja Frydrychowicz      Bug 1597877 - Implement Page.createIsolatedWorld; r=remote-protocol-reviewers,whimboo,ato
b33ca346dd08    Maja Frydrychowicz      Bug 1597877 - Make Runtime.enable/disable control notifications only; r=remote-protocol-reviewers,whimboo,ato
b25ef4bd85a8    Maja Frydrychowicz      Bug 1597877 - Allow many ExecutionContexts per inner window; r=remote-protocol-reviewers,ato,whimboo
70a53dbdd4b7    Maja Frydrychowicz      Bug 1597877 - Identify internal methods in Runtime domain; r=remote-protocol-reviewers,whimboo
9ef2f2fbf2f2    Maja Frydrychowicz      Bug 1597877 - Report name, origin, type in Runtime.executionContextCreated; r=remote-protocol-reviewers,ato,whimboo
ce88fdca1fea    Maja Frydrychowicz      Bug 1597877 - Make frameId a string; r=remote-protocol-reviewers,ato,whimboo
00c691f11046    Noemi Erli      Backed out 9 changesets (bug 1596918) for causing multiple browser-chrome failures
b65a53a83b48    Kris Maglione   Bug 1596918: Part 3b - Run code formatters on files changed by previous patch. r=mccr8,remote-protocol-reviewers,ato
6e89cdf9c855    Kris Maglione   Bug 1596918: Part 3a - Scripted rewrite of most ContentTask.spawn calls to SpecialPowers.spawn calls. r=mccr8,remote-protocol-reviewers,ato
444cc56888cc    Daniel Varga    Backed out 17 changesets (bug 1596918) for multiple browser-chrome and dev-tools failures. On a CLOSED TREE
7c49f5cd9b3b    Kris Maglione   Bug 1596918: Part 3b - Run code formatters on files changed by previous patch. r=mccr8,remote-protocol-reviewers,ato
799653ebd029    Kris Maglione   Bug 1596918: Part 3a - Scripted rewrite of most ContentTask.spawn calls to SpecialPowers.spawn calls. r=mccr8,remote-protocol-reviewers,ato

Work

Milestones
Development status of Puppeteer alpha
Puppeteer alpha dashboard
Bugzilla queries
All project work currently in development
Available MVP work
Completed MVP work
Bug overviews
Gutenberg dependency tree
Puppeteer examples dependency tree
Complete Puppeteer dependency tree
All ze boogs

PTO (🎄)

  • maja_zf: Dec 23rd to Jan 9th or 10th
  • ato:
    • Tuesday 17th December
    • Monday 23rd December to Friday 3rd January 2020
Retrieved from "https://wiki.allizom.org/index.php?title=WebDriver/RemoteProtocol/Meetings/2019/12/13&oldid=1234145"