Open Bug 1874098 Opened 11 months ago Updated 11 months ago

Review test_redirect* wdspec tests for BiDi network events

Categories

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

task
Points:
2

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned, NeedInfo)

References

Details

(Whiteboard: [webdriver:backlog])

For most of our network events, we have a few similar test cases around redirects:

  • test_redirect or test_redirect_fetch which tests a 302 redirect when using fetch
  • test_redirect_http_equiv tests a "redirect" using a page with the http-equiv meta
  • test_redirect_navigation tests a 302 redirect for a navigation

test_redirect_fetch and test_redirect_navigation both use the same http handler, so we might only keep one of the tests.
Note that the navigation one is interesting because it allows to test that the 2 network events have the expected navigation id. So if we only keep one, we should probably keep the navigation one.

Points: --- → 2
Flags: needinfo?(jdescottes)
Priority: -- → P3
Whiteboard: [webdriver:backlog]
You need to log in before you can comment on or make changes to this bug.