Closed Bug 1642771 Opened 4 years ago Closed 10 months ago

Investigate regression in Puppeteer 3 unit tests

Categories

(Remote Protocol :: CDP, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: impossibus, Unassigned)

References

(Regression)

Details

(Keywords: regression)

The mouse/click tests listed in https://phabricator.services.mozilla.com/D77625#2369998 are more flaky since we updated from v2.1.0 to v3.1.0 of Puppeteer in Bug 1632710

Regressed by: 1632710
Summary: Investigate regression in mouse puppeteer unit tests → Investigate regression in mouse Puppeteer 3 unit tests
Severity: -- → S3
Component: CDP: Input → CDP

Regressions from the mentioned Phabricator revision are:

Page.click should click the button: PASS, FAIL
Keyboard should press the metaKey: FAIL
Mouse should resize the textarea: FAIL, PASS
Mouse should select the text with mouse: FAIL, PASS
Page.waitForNavigation should work: PASS, FAIL
Network Events Page.Events.Response: PASS, FAIL
Frame.waitForSelector should throw when frame is detached: FAIL
ignoreHTTPSErrors Response.securityDetails should work: FAIL
DefaultBrowserContext page.setCookie should work: FAIL
DefaultBrowserContext page.deleteCookie should work:FAIL

With bug 1740798 fixed the Mouse related failures should no longer be present. As such here the remaining flaky tests:

Keyboard should press the metaKey: FAIL
Page.waitForNavigation should work: PASS, FAIL
Network Events Page.Events.Response: PASS, FAIL
Frame.waitForSelector should throw when frame is detached: FAIL
ignoreHTTPSErrors Response.securityDetails should work: FAIL
DefaultBrowserContext page.setCookie should work: FAIL
DefaultBrowserContext page.deleteCookie should work:FAIL
Summary: Investigate regression in mouse Puppeteer 3 unit tests → Investigate regression in Puppeteer 3 unit tests

Puppeteer is now at version 20 and a lot of tests have been changed. Nothing we should spend our time on.

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