Change management impacts testing as much as it does development. Testing adapts as we leave behind batch jobs for streaming and static virtual machines for ephemeral containers. New ways of delivering software—continuous delivery instead of manual releases—bring with them new ways for something to fail, new ways things can slow down, and new rules to follow. Old monolithic systems no longer work with microservices, and going from a single long-lived release train to many short-lived feature branches no longer works with traditional integration systems testing on a long-lived staging environment.