Ankur

The browser module is making changes to abstract away the chromium browser lifecycle away from the user. This will allow the browser module to better utilise the test generator resources...

Something else that would help the browser module is a "start of test run" (similar to the `setup` JS method). The differences being that it would be an API at...

Needs to be evaluated.

We've not updated the `ElementHandle` docs, i didn't get a chance to update them when i did the last large doc update. Happy for you to take it on @mdcruz

This issue has been resolved by PR https://github.com/grafana/xk6-browser/pull/1035 which corrects the confusion over what the timeout was (ms or s) and uses `time.Duration` to store the timeout. The APIs (`browserContext.setDefaultTimeout`...

I believe this is an up to date list of APIs that we should move over to be asynchronous (i.e. wrap the return in a `Promise`). The list was created...

Good point, let's close this 🎉

@codebien @inancgumus I've taken a look at this for the browser project. I think this is a great idea. Unfortunately the browser codebase deviates quite a bit from the k6...

@codebien @inancgumus apart from the lint, there are also the following jobs: - `dependencies` - `test-go-versions` - `test-build` `test-go-versions` isn't going to work with the browser codebase since we need...

> In any case, you should review the current cases to check if we have some with high priority. Maybe, we have to allocate someone from our team to support...