Pepe Cano
Pepe Cano
https://k6.io/blog/how-to-lint-k6-tests-and-add-a-pre-commit-hook/ touches more extensively this topic. Perhaps, instead of a dedicated section, we could cover this as part of a more general tutorial for recommendations to set up your k6...
@matthewbordas, this project has a [.eslintrc file](https://github.com/grafana/k6-docs/blob/main/docs/.eslintrc.js) used to validate the documentation examples.
@MattDodsonEnglish, consider this for the blog post about the different options to visualize k6 results.
@MattDodsonEnglish No bad consequence. As states on the [Algolia wiki page](https://github.com/grafana/k6-docs/wiki/Algolia-returns-old-URLs:-solution); clear the Index and do a new deployment.
> I wonder if github action is supposed to run a test without a requirement to install the xk6-browser. I think so! For reference while we wait for the implementation,...
This is now supported in the new GitHub action: https://github.com/grafana/setup-k6-action (`browser`: true)
This is now supported in the new GH action: https://github.com/grafana/run-k6-action/
In addition to the previous suggestion, it could also support: ```js export const options = { browser: true } ``` This configuration should use all the default settings for browser...
suggest merging this when we update the existing tutorial
Hi @Nathan-Bernardo, I wonder why do you need to extend `_ENV`? If you need the `VUS` value, you can get it from the [`test.options` object (`k6/execution`)](https://k6.io/docs/javascript-api/k6-execution/#test).