Good test coverage is essential for catching issues before a pull request has been merged, but they have to be the right kind of tests and must be reliable. Sam Guckenheimer digs into the testing transformation his team at Microsoft underwent as they started on their DevOps journey. He explains how they used to test their products and the issues (both technical and cultural) this presented. He walks you through the changes they went through and why and explains the data they found to prove their case for change and what they did to move. Sam also details which things are best covered by unit tests, which you should leave to manual code review in the pull request, and which are best suited to testing in production.
Sam Guckenheimer is the product owner for Azure DevOps at Microsoft, where he acts as the chief customer advocate, responsible for the strategy for the next releases of these products, focusing on DevOps, Agile, and CI/CD pipelines. Sam also curates the website DevOps at Microsoft. Previously, Sam was director of product line strategy at Rational Software Corporation, now the Rational Division of IBM. He is a regular speaker and has given keynote addresses at conferences such as DevOps Enterprise Summit and Agile. He is the author of four books, most recently Journey to Cloud Cadence and Visual Studio Team Foundation Server 2012: Adopting Agile Software Practices—From Backlog to Continuous Feedback. Sam lives in the Seattle area with his wife in a sustainable house they built.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com