O'Reilly logo
  • Anton Klautsan thinks this is interesting:

How Submit Queues and Continuous Builds Came Into Being by Jeff Carollo

In the beginning, Google was small. Having a policy of writing and running unit tests before checking in changes seemed good enough. Every now and then, a test would break and people would spend time figuring out why and then fix the problem.

The company grew. To realize the economies of scale, high-quality libraries and infrastructure were written, maintained, and shared by all developers. These core libraries grew in number, size, and complexity over time. Unit tests were not enough; integration testing was now required for code that had significant interactions...

From

Cover of How Google Tests Software

Note

How Submit Queues and Continuous Builds Came Into Being