Open Bug 1571421 Opened 5 years ago Updated 2 years ago

Remove "await" workarounds in tests after switching hosts (toolbox in a content frame)

Categories

(DevTools :: Framework, task, P3)

task

Tracking

(Fission Milestone:Future)

Fission Milestone Future

People

(Reporter: jdescottes, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

The change introduced by Bug 1539979 is introducing some intermittent behaviors.

Some of them are related to switchHost, which seems to be more async than it used to. Maybe there is a different event on which we need to wait for when DevTools are running in a content frame.

The current plan for such failures is to wait in the tests after calling switchHost. We should find a better solution and remove the calls to wait()

Some other intermittents don't seem directly related to switchHost. For those my current plan is to force DevTools back to a chrome frame, just for the duration of the test via

await pushPref("devtools.toolbox.content-frame", false);

The identified intermittents for now are:

  • devtools/client/webconsole/test/mochitest/browser_jsterm_screenshot_command_clipboard.js
  • devtools/client/shared/test/browser_html_tooltip_consecutive-show.js

Until those intermittents are fixed, we need to keep some support for DevTools running in a chrome frame. But if it remains test-only, then the platform workaround could still be removed.

There is some focus workaround in https://phabricator.services.mozilla.com/D40994 which may be removed?

A few wait() calls have been added in https://phabricator.services.mozilla.com/D40995

Thanks!

Tests that have await statements that should be cleaned up:

  • devtools/client/inspector/markup/test/browser_markup_events-windowed-host.js
  • devtools/client/inspector/rules/test/browser_rules_eyedropper.js
  • devtools/client/inspector/test/browser_inspector_pane-toggle-04.js
  • devtools/client/netmonitor/test/browser_net_prefs-reload.js
  • devtools/client/shared/test/browser_html_tooltip_zoom.js

Tests that force devtools.toolbox.content-frame to false:

  • devtools/client/webconsole/test/mochitest/browser_jsterm_screenshot_command_clipboard.js
  • devtools/client/shared/test/browser_html_tooltip_consecutive-show.js
  • devtools/client/shared/test/browser_treeWidget_keyboard_interaction.js
  • devtools/client/shared/test/browser_treeWidget_mouse_interaction.js
Whiteboard: dt-fission
Summary: Fix test workarounds introduced to use DevTools in a content frame → Remove "await" workarounds in tests after switching hosts (toolbox in a content frame)

Let's split the bug in two. This one will be only about fixing the tests where we added 1s wait after switching hosts.

Blocks: 1578979
See Also: → 1578979
Priority: P2 → P1

Marco: sorry I mixed the priority of the two bugs :) This one is not critical to fix, the other one is (Bug 1578979).

Assignee: jdescottes → nobody
Status: ASSIGNED → NEW
Priority: P1 → P3
Whiteboard: dt-fission → dt-fission-reserve

Tracking Fission DevTools bugs for Fission Nightly (M6)

Fission Milestone: --- → M6

dt-fission-reserve bugs do not need to block Fission Nightly (M6).

Fission Milestone: M6 → ---

Tracking dt-fission-reserve bugs for Fission MVP until we know whether they really need to block Fission or not.

Fission Milestone: --- → MVP

Moving old "dt-fission-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.

Fission Milestone: MVP → Future
Whiteboard: dt-fission-reserve → dt-fission-future
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.