liveBook · Manning

Load testing

As explained in Build High Value Software Systems

Testing that evaluates system behavior and performance under a specified workload.

Load testing checks system behavior under a specified workload. Used before database changes reach staging, it can reveal performance problems early enough to prevent them from reaching production. section 1.2.3

An automated load-test gate can:

  • Run when a pull request changes specified database tables. section 1.2.3
  • Simulate realistic query volumes against production-like data, then fail the build when query-time thresholds are exceeded or locks are detected. section 1.2.3
  • Post results directly to the pull request so performance feedback arrives before staging. section 1.2.3

Catching a table-lock problem

A production rollback caused by a table lock could have been caught by requiring load tests for database-heavy changes before staging. section 1.2.4

How Build High Value Software Systems covers it

How deep it goes
Describes automated triggers, realistic query volumes, query-time thresholds, and lock detection, without detailing test implementation.
Examples
Uses database changes, realistic query volumes, threshold failures, and a table-lock rollback as concrete examples.
What you can do after
Operate a build gate that runs load tests for selected database changes and flags slow queries or locks.
How it connects
Connects load testing with automated testing, pull requests, production-like data, staging, and production incidents.

Also explained in

Compare how 7 books explain load testing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.