Template `browser.newContext` and `browser.newPage` options doc pages
- Dominant language
- Python
- Stars
- 117
- Forks
- 266
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 9
Description
The options for `browser.newContext` and `browser.newPage` are currently the same, and are a good candidate to apply some templating to keep both in sync with each other.
More context on this issue can be found here:
- https://github.com/grafana/k6-docs/pull/722#discussion_r916628705
- https://loadimpact.slack.com/archives/CCV4TK1DL/p1657554925026749
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the documentation pages for the browser.newContext and browser.newPage options and compare their current contents. Read the linked pull request discussion for the intended templating approach. Done means both pages share a maintainable template while documenting the same options consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100