Open Bug 1744935 Opened 3 years ago Updated 3 years ago

Ensure setup/teardown for wdspec tests cleans all the bidi-specific state

Categories

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

Product:
Remote Protocol
Component:
WebDriver BiDi
Type:
task
Points:
8

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

Details

(Whiteboard: [webdriver:backlog])

We have been adding small cleanups in individual tests so, for instance see the thread at https://phabricator.services.mozilla.com/D132845#inline-732885

Instead the test harness should define setup / teardown steps which ensure a clean state for each test.

Whiteboard: [webdriver:triage] → [bidi-m3-mvp]

Todo:

  • unsubscribe from all BiDi events in case we reuse the same session
  • ideally use a new tab for each test

James: would it make sense to add a command to unsubscribe from all events in the spec or should this just be an internal command?

Points: --- → 8
Flags: needinfo?(james)
Priority: -- → P3
Summary: Add a setup/teardown for bidi wdspec tests to ensure a clean state → Ensure setup/teardown for wdspec tests cleans all the bidi-specific state

Do you actually want a command that just unsubscribes from events, or one that unsets all session state without ending the session? For example, what should happen to the object cache, or input state (once we have that). Does a command to reset all state make sense if ending and starting a session doesn't require restarting the browser? It seems like they're mostly equivalent?

Flags: needinfo?(james)
Priority: P3 → P2
Whiteboard: [bidi-m3-mvp] → [webdriver:backlog]
You need to log in before you can comment on or make changes to this bug.