Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reevaluate browser configuration #854

Closed
9 tasks done
ankur22 opened this issue Apr 13, 2023 · 0 comments
Closed
9 tasks done

Reevaluate browser configuration #854

ankur22 opened this issue Apr 13, 2023 · 0 comments
Assignees
Labels
breaking PRs that need to be mentioned in the breaking changes section of the release notes team/k6browser To distinguish the issue on project boards.
Milestone

Comments

@ankur22
Copy link
Collaborator

ankur22 commented Apr 13, 2023

We want to make it simpler for the user to work with the browser, so that they don't need to worry about the lifecycle of the browser and to help us with the end goal of abstracting away the confusing browserContexts object.

This issue is to evaluate and prove that we can isolate and abstract the browser from the end user for majority of use cases. Some use cases will still require the configuration of the browser which we have a plan for too.

Tasks

  1. team/k6browser
    ka3de
  2. poc team/k6browser
    ka3de
  3. enhancement ux
    ka3de
  4. breaking
    ka3de
  5. breaking
    ka3de
  6. breaking
    ka3de
  7. breaking
    ka3de
  8. breaking
    ka3de
  9. breaking
    ka3de
@ankur22 ankur22 added this to the v0.10.0 milestone Apr 13, 2023
@ankur22 ankur22 added breaking PRs that need to be mentioned in the breaking changes section of the release notes team/k6browser To distinguish the issue on project boards. labels Apr 13, 2023
@ka3de ka3de self-assigned this Apr 17, 2023
@ka3de ka3de removed their assignment Apr 17, 2023
@ka3de ka3de self-assigned this Apr 26, 2023
@ka3de ka3de changed the title POC for browser configuration Reevaluate browser configuration Apr 27, 2023
@ka3de ka3de closed this as completed May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking PRs that need to be mentioned in the breaking changes section of the release notes team/k6browser To distinguish the issue on project boards.
Projects
None yet
Development

No branches or pull requests

2 participants