This repo contains resources for:
- creating slide presentations
- giving a workshop
- speaking about k6
- learning about k6
You can also use the following resources to learn or teach k6. You copy and modify these projects to your use case and audience. They are intended to be a jumping off point, so you can remove content that wouldn't appeal to your audience or add new ones to show off your style more.
Consider running a workshop for k6. Below is an outline of what that workshop could look like, as well as modules you could use for each topic. Feel free to take these and include the parts most relevant to you!
We have also created built-in slides for you, which you are free to edit. To customize the slides, please fork this repo and make edits according to how you want the workshop to be structured.
The slides are created using reveal.js and are all found in the slides folder.
In your terminal, run the following command:
npm install
npm run slides
- Introduction to Performance Testing
- Frontend vs. backend performance testing
- Load testing
- High-level overview of the load testing process
- Getting started with k6 OSS
- The k6 CLI
- Understanding k6 results
- Adding checks to your script
- Adding think time using sleep
- k6 Load Test Options
- Setting test criteria with thresholds
- k6 results output options
- Recording a k6 script
- How to debug k6 load testing scripts
- Dynamic correlation in k6
- Workload modeling
- Adding test data
- Parallel requests in k6
- Organizing code in k6 by transaction - groups and tags
- Setup and Teardown functions
- Setting load profiles with executors
- Workload modeling with scenarios
- Using execution context variables
- Creating and using custom metrics
k6-learn would not be possible without these amazing contributors! 🌟
- Imma Valls
- Krzysztof Widera
- Leandro Melendez
- Marie Cruz
- Matt Dodson
- Nicole van der Hoeven
- Paul Balogh
- If there an issue does not exist, start by creating it under https://github.com/grafana/k6-learn/issues.
- Fork this repository.
- Make the changes in your forked repository. Note that new branches, changes and pushes will only affect your repository.
- Once ready, create a Pull Request from your fork, mentioning the issue it solves (step 1). Keep in mind you might need to sync it.
- Once you have created the Pull Request, your changes now will be reviewed and either accepted or you will be asked for modifications. For more information about forking visit the page: https://docs.github.com/en/get-started/quickstart/fork-a-repo