feat: Make sure to wait for DOM events

[ebebbington]

Summary

What:

Wait for:

• Dom to be ready eg Dom.readyState
• Allow users to wait a certain amount of time
  • they can pass a callback to instead wait until a specific condition passed eg until button text equals something

Why:

We need to be sure that the Dom is loaded properly when the location is awaited, to test this, we could add a basic Dom content loaded handler that adds text to the Dom, assert we see the text

another thing I want to make sure we can cover is say the JS is what loads the content on the page eg API calls, React/Vue, where a basic view is displayed, and API calls are made once pagebis loaded to get a use rod users or whatever

There is also wait(‘$.active’) I used in Laravel, investigate this to see if it can help in waiting for these things

Acceptance Criteria

Below is a list of tasks that must be completed before this issue can be closed.

• [ ] Write documentation
• [ ] Write unit tests
• [ ] Write integration tests
• [ ] {add more checkboxes required by this issue as needed}

Example Pseudo Code (for implementation)

// Add example pseudo code for implementation

[ebebbington]

1. We do this already
2. Providing a wait function doesn't provide enough use, a user can use std/async/delay to wait
3. user can write their own logic if they want to wait
4. waiting for requests following click already covered by click method
5. waitinf for dom to load ie react components fetch data can be covered by std/async/delay

[ebebbington]

Be good to do what puppeteer does, via networkidle0, but i just have no clue how to implement it