Closed Bug 1868576 Opened 1 year ago Closed 1 year ago

Fix bidi network wdspec tests test_response_headers

Categories

(Remote Protocol :: WebDriver BiDi, task, P3)

task
Points:
1

Tracking

(firefox122 fixed)

RESOLVED FIXED
122 Branch
Tracking Status
firefox122 --- fixed

People

(Reporter: jdescottes, Assigned: jdescottes)

References

Details

(Whiteboard: [webdriver:m9], [wptsync upstream])

Attachments

(1 file)

There are two bidi network wdspec tests called test_response_headers:

They used to pass by mistake because we were not asserting the response, but they now fail because the mimeType does not match.

We can either change the support file to add a Content-Type header or update the tests in order to stop asserting the mimeType.

Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Points: --- → 1
Priority: -- → P3
Whiteboard: [webdriver:m9]
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/518de58d5daa [wdspec] Set ContentType header in http_handlers/headers for bidi network tests r=webdriver-reviewers,whimboo
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/43557 for changes under testing/web-platform/tests
Whiteboard: [webdriver:m9] → [webdriver:m9], [wptsync upstream]
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
Upstream PR was closed without merging
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: