docs: add a few more k6 browser examples #1430
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdcruz
force-pushed
the
update-k6-browser-examples
branch
from
324c17b
to
4733668
Compare
inancgumus
reviewed
Nov 29, 2023
|
|
||
| # Hybrid performance with k6 browser | ||
|
|
||
| An alternative approach to [browser-based load testing](https://grafana.com/docs/k6/<K6_VERSION>/testing-guides/load-testing-websites/#browser-based-load-testing) that is much less resource-intensive is combining a low amount of virtual users for a browser test with a high amount of virtual users for a protocol-level test. |
There was a problem hiding this comment.
Is <K6 VERSION> here correct?
There was a problem hiding this comment.
Yes, I've looked at the existing examples and seems to be correct :)
There was a problem hiding this comment.
That's correct! It's how we handle versioned links in the Grafana docs, it'll change based on which version of the docs the user is in. So if they're seeing latest, the links on that page will replace <K6_version> with latest.
There was a problem hiding this comment.
Looks good overall! I made a few comments most of them are just to rewrite a few sentences to use active voice instead of passive to follow our style guide. 🤓
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
docs/sources/next/using-k6-browser/recommended-practices/hybrid-approach-to-performance.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Heitor Tashiro Sergent <heitortsergent@gmail.com>
inancgumus
approved these changes
Nov 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This PR adds a few more examples of using k6 browser, mainly using custom metrics and hybrid performance.
Checklist
Please fill in this template:
make docscommand locally and verified that the changes look good.Select one of these and delete the others:
If updating the documentation for the most recent release of k6:
docs/sources/v{most_recent_release}folder of the documentation.docs/sources/nextfolder of the documentation.If updating the documentation for the next release of k6:
docs/sources/nextfolder of the documentation.Related PR(s)/Issue(s)