docs: update k6 browser documentation

[mdcruz]

Updates k6 browser documentation based on a few issues:

• Explain how to take screenshot using k6 browser docker #1318
• Document how users can connect to remote browsers  #1314
• Add chromium-based browser requirement for using k6-browser #1263

[github-actions]

There's a version of the docs published here:

https://mdr-ci.staging.k6.io/docs/refs/pull/1345/merge

It will be deleted automatically in 30 days.

[inancgumus]

Great! Thanks for working on this 🙇 I have some suggestions.

[mdcruz]

Great! Thanks for working on this 🙇 I have some suggestions.

Awesome, thank you! 💜

[inancgumus]

👏

[heitortsergent]

Some small nits, but LGTM!

For the screenshot issue (#1318), do we want to include more of a separate page or section, or do you think this is enough to close it?

[inancgumus]

@mdcruz Should we change the base branch to update/browser-v1.1.0? It's because the new docker feature hasn't been added yet.

[ka3de]

@mdcruz Should we change the base branch to update/browser-v1.1.0? It's because the new docker feature hasn't been added yet.

Do you mean the removal of SYS_ADMIN capability as a requirement? I believe it was already added, it's now released in the current docs version here. Also the current grafana/k6:master-with-browser image should include this change, as I believe it's pushed to the registry through the CI so it does not depend on the k6 release process.

[inancgumus]

Ah, OK then 👍 Thanks for clarifying it 🙇

…

On Thu, Sep 28, 2023 at 12:15 PM ka3de ***@***.***> wrote: @mdcruz <https://github.com/mdcruz> Should we change the base branch to update/browser-v1.1.0? It's because the new docker feature hasn't been added yet. Do you mean the removal of SYS_ADMIN capability as a requirement? I believe it was already added, it's now released in the current docs version here <https://k6.io/docs/using-k6-browser/running-browser-tests/>. Also the current grafana/k6:master-with-browser image should include this change, as I believe it's pushed to the registry through the CI so it does not depend on the k6 release process. — Reply to this email directly, view it on GitHub <#1345 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEXVMAEK6JN4TJRKL3SPSLX4U53FANCNFSM6AAAAAA5JM7PPM> . You are receiving this because your review was requested.Message ID: ***@***.***>

[mdcruz]

Some small nits, but LGTM!

For the screenshot issue (#1318), do we want to include more of a separate page or section, or do you think this is enough to close it?

I think, for now, this example is enough because we only have one section to cover how to run tests and the example script contains page.screenshot()