Test your k6 knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What does k6's support for multiple "executors" (like `constant-vus`, `ramping-vus`, `constant-arrival-rate`) provide, beyond a simple fixed number of virtual users?
Questions in this quiz
What does k6's support for multiple "executors" (like `constant-vus`, `ramping-vus`, `constant-arrival-rate`) provide, beyond a simple fixed number of virtual users?
How does k6 typically fit into a CI/CD pipeline for catching performance regressions before they reach production?
What does a k6 "check" do, and how does it differ from a hard test assertion that stops execution on failure?
How does k6's architecture (a Go-based runtime executing JavaScript test scripts) contribute to its ability to generate significant load from a single machine?
What is k6?
What is the purpose of parameterizing test data in a k6 script (e.g. using different usernames or search terms per iteration), rather than always sending the exact same hardcoded request?
What is the difference between k6's "load testing", "stress testing", and "spike testing" scenario types, at a conceptual level?
What is the purpose of running a k6 load test against a staging/pre-production environment rather than directly against production?
What is the purpose of k6's "custom metrics" feature (via `Counter`, `Gauge`, `Trend`, `Rate` from the `k6/metrics` module)?
What is a k6 "threshold", and what problem does it solve for automated performance testing (e.g. in CI)?