How Google Tests Software (EBOOK)
When I found out about the book How Google Tests Software it didn t take long until I had ordered a copy I find it uite take long until I had ordered a copy I find it uite to read about how Google does things whether it is about their development process their infrastructure their hiring process or in this case how they test their software I am a developer at heart but I have worked for a few years as a tester so testing is also dear to meIt s uite an interesting book and it makes some reat points about the future of testing However despite the phrase Help me test like Google on the cover it is not as useful as I had hoped when it comes to improving your own testingThe book starts off by describing the key roles at Google SWE Software Engineer SET Software Engineer in Test and TE Test Engineer Briefly the SWE builds features for Google s products the SET develops testing infrastructure and larger scale automatic tests and the TE tests the products from a user s perspective After the introductory chapter there is a chapter each on the SET and TE roles and there is also a chapter on the TEM Test Engineer Manager role The final chapter is about the future of testing at Google and in eneralSoftware Engineer in Test SETAs the different roles are explained in the respective chapters there is also uite a bit "of detail on how the testing is done at Google The most interesting part in the chapter "detail on how the testing is done at Google The most interesting part in the chapter the SET role is the part about the infrastructure There is of course extensive support for running tests automatically There is common infrastructure for compilation execution analysis storage and results reporting of tests Tests
categorized as small medium large or enormous Small tests are basically tests where everything external is mocked out and they are expected to execute in less than 100 msMedium tests involve external subsystems and can use database access but enerally run on one machine use no network services and are expected to run in under a second Large and enormous tests run a complete application including all external systems needed They can be nondeterministic because of the complexity and they are expected to complete in 15 minutes and 1 hour respectively A Betrayals good way to summarize them is that small tests lead to code uality and medium large and enormous tests lead to product uality The common test execution environment for running the tests has been developed over time and has several nice features It will automatically kill tests that take too long to run thus the time limits mentioned aboveIt has several features to facilitate running many different test concurrently on a machine it s possible to reuest an unused port to bind to instead of a hardcoded port number that could clash with another test writing to the file system can be done to a temporary location uniue to the current test and private database instance can be created and used to avoid cross talk from other tests Further their continuous integration system uses dependency analysis to run only tests affected by a certain change thus being able to pinpoint exactly which change broke a certain test This system has been developed by Google for many years and has become uite capable and tailored to their way of workingTest Engineer TEThe most interesting part in the TE chapter is the description of the process used fo. Google faces the world's largest toughest software testing challenges Toet it right Google is pioneering the future of testing and automation You also need to et it right Learn from Google In How Googl. S a wholeOverall I thought the book had a lot of potential but the pacing issues with the size of each chapter and the dearth of useful technical details really took a lot of the wind out of its sails I learnt about uite a few useful tools especially pyAuto for driving Chrome automation as well as Protocol Buffers for creating class definitions and serializing data easily However "most of the content in this book is management than technical focused and would probably benefit someone who is already "of the content in this
are categorized as small medium large or enormous Small tests are basically
BOOK IS MANAGEMENT THAN TECHNICAL FOCUSED AND WOULD PROBABLY is management than technical focused and would probably someone who is already with the testing scene as it currently is than new readers trying to find ways to improve their software uality This is not a typical book It has both ood and bad The Bat Ode good the level of technical detail the clarity and the straightforward presentation of the authors The book painted a picture where SET software engineer in test was the best technical job and TE test engineers are the besteneralist job At least from a reader s point of view It certainly is encouraging and enlightening particularly for Bitter Choices: Blue-Collar Women in and out of Work google engineersThe bad1 the writing style Oh myod the authors have almost no writing style The whole book reads like a training handout it has verbatim interviews interspersed in the chapters Short articles written by SETs TEs inserted into the text Long code segments interspersed with cultural discussions Verbatim copies of blog posts There is no consistent flow of thoughts The book seriously lack readability improvement2 the vision itself All three authors have left Google after this book was published I cannot help but asking does the vision stand ood with time or it is just an wishful thinking of the roup of engineers at the peak years of the testing effort of Google As a budding uality Assurance Analyst at a relatively small software company I decided to Beyond Redemption: Race, Violence, and the American South after the Civil War give this book a read toet an understanding of how a big company like Google approaches software testing I found it to full of extremely helpful information and it opened my eyes to how the rest of the tech industry approaches software testing It Blank Darkness: Africanist Discourse in French goes into detail about how Google ensures that its product line is of the highest uality featuring the various types of positions in the Engineering Productivity department at Google the Software Engineer in Test the Test Engineer and the Test Engineering Manager The skills and responsibilities for each position is fleshed out inreat detail and this book did an excellent job of describing Google s software testing practices in an easy to understand manner If you re in software testing and are curious about this topic you won t be disappointed Must read for everyone whose work related to software testing and uality assurance This book provides interesting views into how an organization Google worked to introduce uality into their software development efforts I particularly enjoyed the interviews with the team tasked with rolling out a new approach to testing within the organization Tasking a small Back to the Breast: Natural Motherhood and Breastfeeding in America group of experts to drive a new program new mindset new approaches into an organization is tough Andetting exposure to how other s have faired is valuable Speaking of mindsets in the spirit of travelling light and delivering value I also enjoyed the coverage of the Attribute Component Capability approach to figuring out and communicating test plan. Kthrough best practices you can use even if you're not uite Google's sizeyet Using these techniues you can transform testing from a bottleneck into an accelerator and make your whole organization producti. .
James A. Whittaker Ü 4 Free read.
R developing the test plan for a product The test plan s purpose is to map out what needs to be tested for the product and when it is done it should be clear what test *cases are needed It can be a challenge to find the right level of detail for a * are needed It can be a challenge to find the right level of detail for a plan but it seems like they have found a ood balance at GoogleThe Google process for coming up with the test plan is called ACC which stands for
Attribute Component and Capability Attributes are the ualities of the product theComponent and Capability Attributes are the ualities of the product the selling points that will et the people to use the product The examples iven for Chrome include fast secure and stable There "won t typically be that many attributesNext the Components are the major subsystems "t typically be that many attributesNext the Components are the major subsystems the product around 10 seems to be a reasonable number to include Finally there are the Capabilities which are the actions the system can perform for the user Whereas there are relatively few attributes and components there can be uite a number of capabilities The capabilities lie at the intersection of attributes and components It is natural to create a matrix with attributes alon This was an odd book It s really 3 things an internal training manual a recruiting tool and an external uide to Google s testing practices The first two really Black and White Strangers: Race and American Literary Realism got in the way of what would have otherwise been a very interesting book The best book on testing or facilitating engineering productivity as it s known within the book and among theoogle SETs software engineers in testing I ve ever read though most of this will be old hat to anyone who s digested the lessons of test driven development read on the advice of my new manager at Boggs: A Comedy of Values google How does Google test software how it should be tested with developers doing most of their own testing saving the manual testers for the things that are best done by a human I like the philosophy In my day to day job as a software engineer I constantly encounter new and interesting problems in the realm of testing software So when I found How Google Tests Software I was very excited to find out what techniues Google employs to tackle some of these thornier problems at scaleThe opening chapters of the book do a reallyreat job of describing the ethos of testing at Google and very clearly defining what their Blood Runs Green: The Murder That Transfixed Gilded Age Chicago goals are and how each of their roles and tools will contribute to that overalloal Reading through these chapters I found myself chomping at the bit to find the nuggets of wisdom that I could apply in my own workHowever past the opening chapters for me the book really started to wane in terms of technical details and I found myself working harder and harder to find the lessons that I could take away While I appreciated the author s descriptions of the tools that Google uses internally the overviews weren t enough for me to determine exactly what about the tools solved their testing problems and it wasn t enough to really understand how to build a similar infrastructure at my companyThe latter half of the book focused heavily on interview transcripts with testing leaders at Google While I did appreciate their war stories and takeaways I felt the interviews didn t have uite enough useful information to justify the amount of space that they took up in the book Even the last chapter felt like of an anti climax rather than a solid wrap up of the book E Tests Software legendary Google testing leader James Whittaker and two top Google experts reveal powerful lessons Google has learned about testing software at unparalleled scale and speed and offer brea. ,