Closed Bug 1428813 Opened 6 years ago Closed 4 years ago

Redundant tabbrowser check in WebDriver:GetCurrentURL in content context

Categories

(Remote Protocol :: Marionette, enhancement, P3)

Product:
Remote Protocol
Component:
Marionette
Version:
Version 3
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: ato, Unassigned)

Details

When Marionette is in content context there is a test expectation
in test_get_current_url_chrome.py that it should return a no
such window error if the current chrome window does not have a
tabbrowser.

It seems irrelevant to content context whether the currently
selected chrome window has a tabbrowser or not if the content
browser’s window (not selected) does.  The Get Current URL command
is meant to work in the current context that is chosen.

Is is TestGetCurrentUrlChrome.test_no_browser_window from
testing/marionette/harness/marionette_harness/tests/unit/test_get_current_url_chrome.py
that is wrong.
[Mass Change 2018-01-15] Moving bugs to backlog
Priority: -- → P3

This is actually true and not faulty. Note that the whole test file runs in chrome context by default, and as such switches to a tab-less chrome window in chrome context. Only to retrieve the current URL we temporarily switch to the content context. But given that no content window has been set, the command has to raise the "no such window" error type.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.