Test your Gatling knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is the purpose of Gatling's "feeders" (e.g. `csv("users.csv").random`)?
In this round
What is the purpose of Gatling's "feeders" (e.g. `csv("users.csv").random`)?
What is a common reason a performance test might pass functionally (all checks succeed) but still reveal a problem worth investigating?
Why is it important to run a load test from a machine (or set of machines) with sufficient network bandwidth and CPU capacity, separate from the system under test?
What is the significance of Gatling being able to run as part of a CI/CD pipeline, rather than only as a manual, ad-hoc test?
What is the difference between "load testing," "stress testing," and "soak testing" as distinct performance testing goals Gatling can be used for?
What is a Gatling "Simulation," and what does it typically define?
What is Gatling's significant architectural advantage for generating high load compared to a naive thread-per-user testing approach?
What does it mean for a Gatling assertion like `details("Get Homepage").responseTime.percentile(95).lt(500)` to be included in a simulation?
What is the relationship between throughput (requests/second) and response time as concurrency increases during a load test, in a system approaching its capacity limit?
What is the purpose of "checks" (`.check(status.is(200))`) in a Gatling scenario?
What does an "injection profile" (e.g. `rampUsers(1000).during(60.seconds)`) control in a Gatling simulation?
What protocols beyond plain HTTP can Gatling be used to load test?