Closed Bug 1593340 Opened 5 years ago Closed 5 years ago

Basic tests for Page.navigate

Categories

(Remote Protocol :: CDP, task, P3)

Product:
Remote Protocol
Component:
CDP
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1612538

People

(Reporter: ato, Unassigned)

References

(Blocks 1 open bug)

Details

We don’t appear to have any tests specifically for Page.navigate.

Since we only implement a narrow subset of its functionality,
writing a few tests should be straight forward.

Priority: -- → P3
Whiteboard: [puppeteer-alpha]
Priority: P3 → P2
Whiteboard: [puppeteer-alpha] → [puppeteer-alpha-reserve]
Priority: P2 → P3
Priority: P3 → P2
Whiteboard: [puppeteer-alpha-reserve] → [puppeteer-beta-mvp]

Add priority tag because early return from Page.navigate introduces races in the life cycle of execution contexts, and therefore impacts many other commands.

Whiteboard: [puppeteer-beta-mvp] → [puppeteer-beta-mvp][puppeteer-high-priority]
Priority: P2 → P3
Whiteboard: [puppeteer-beta-mvp][puppeteer-high-priority] → [puppeteer-beta-reserve]

This is what I will do when working on bug 1612538.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Whiteboard: [puppeteer-beta-reserve]
Component: CDP: Page → CDP
You need to log in before you can comment on or make changes to this bug.