derrierloisirs.fr
» » How Google Tests Software

Download How Google Tests Software ePub

by Jeff Carollo,James A. Whittaker

Download How Google Tests Software ePub
  • ISBN 0321803027
  • ISBN13 978-0321803023
  • Language English
  • Author Jeff Carollo,James A. Whittaker
  • Publisher Addison-Wesley Professional; 1 edition (April 2, 2012)
  • Pages 320
  • Formats lit docx mobi doc
  • Category Technology
  • Subcategory Programming
  • Size ePub 1286 kb
  • Size Fb2 1334 kb
  • Rating: 4.1
  • Votes: 765

2012 Jolt Award finalist!

Pioneering the Future of Software Test

Do you need to get it right, too? Then, learn from Google. Legendarytesting expertJames Whittaker, until recently a Google testing leader,and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you’re not quite Google’s size…yet!

Breakthrough Techniques You Can Actually Use

Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests…thinking like real users…implementing exploratory, black box, white box, and acceptance testing…getting usable feedback…tracking issues…choosing and creating tools…testing “Docs & Mocks,” interfaces, classes, modules, libraries, binaries, services, and infrastructure…reviewing code and refactoring…using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator–and make your whole organization more productive!


Jeff Carollo is a software engineer in test at Google and has been responsible for testing Google Voice, Toolbar, Chrome, and Chrome OS. He has consulted with dozens of internal Google development teams helping them improve initial code quality.

Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you're no. .

2012 Jolt Award finalist! Pioneering the Future of Software Test. Do you need to get it right, too? Then, learn from Google.

Электронная книга "How Google Tests Software", James A. Whittaker, Jason Arbon, Jeff Carollo. Эту книгу можно прочитать в Google Play Книгах на компьютере, а также на устройствах Android и iOS. Выделяйте текст, добавляйте закладки и делайте заметки, скачав книгу "How Google Tests Software" для чтения в офлайн-режиме.

How Google Tests Software. To read this book, upload an EPUB or FB2 file to Bookmate.

books/Как тестируют в Google-How Google Tests Software Дж. Уиттакер, Дж. Арбон, Дж. Каролло James A. Whittaker, Jason Arbon, Jeff Carollo-2014. Fetching contributors.

How Google Tests Software book. James A. Whittaker, Jason Arbon. I find it quite fascinating 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 me. by Jason Arbon, James A. Whittaker, Jeff Carollo.

This book is about how the people (developers and managers) at Google engineered an organization that incorporates quality into its foundations

This book is about how the people (developers and managers) at Google engineered an organization that incorporates quality into its foundations. This is no mean task, considering that software quality is one of the cornerstones of any sustained software product. How Google tests software by James A. Whittaker, Jason Arbon and Jeff Carollo. cle{Tan2012HowGT, title {How Google tests software by James A. Whittaker, Jason Arbon and Jeff Carollo}, author {Kwee Heong Tan}, journal {ACM SIGSOFT Software Engineering Notes}, year {2012}, volume {37}, pages {44-45} }. Kwee Heong Tan. Published in. ACM SIGSOFT Softwar. 012.

How Google Tests Software by James Whittaker. In this book written with Jason Arbon and Jeff Carollo, he describes how Google organizes its software testing process. September 3, 2012 Software Testing Magazine Books, Knowledge 2. James Whittaker is a former engineering director at Google and has been responsible for testing Chrome, Google Maps and Google Web Apps. The Google software testing organization that has three roles: Software Engineer in Test (SET), Test Engineer (TE), Test Engineering Manager.

Jeff Carollo is a software engineer in test at Google and has been responsible for testing Google Voice, Toolbar, Chrome, and Chrome OS. He also worked at Microsoft prior to joining Google. Country of Publication.

Talk about How Google Tests Software


Axebourne
I saw James Whittaker speak at STAR West in 2011, and he gave a keynote titled "Test Is Dead". His talk was essentially a teaser for How Google Tests Software that he co-wrote with Jason Arbon and Jeff Carollo. The premise of the book is that testers need to have engineering skills (sometimes to an equal extent as software engineers) in order for the testing discipline to reach first class citizenship on equal footing with development.

The argument is aligns well with the movement toward agile software development methods. The book goes on to breakdown testing responsibilities for software engineers (SWEs), software engineers in a test role (SETs), and Test Engineers (TEs). Almost half of the book deals with the roles and responsibilities of the TE, and in the Google model, they do have a higher-level role in testing. In essence, it breaks down like this:

* SWEs write unit tests for the software they write
* SETs write tools to enable testing without external dependencies and write automated functional tests
* TEs coordinate the overall testing activities for a product and focus on the user by doing exploratory testing

In addition, the book also outlines a number of tools (many of which have been open-sourced) that Google uses for testing in the context of these roles. The majority of the content focuses on web applications (it's Google after all), and some of the ideas won't apply if the majority of your development is for internal customers to your company - since you probably have user training and rules about frequency of release. However, I would say that you could apply 80% of the ideas in any context and probably adapt at least 10% (if not more) of the others to your situation.

Also, there is also a chapter on test managers and directors that has interviews with a number of prominent Googlers. Then, the book ends with a discussion on the future of the SET and TE roles at Google along with some of the errors Google made.

Google embarked on the transformation in 2007, and my company is currently trying to do something similar. I hope to be able to leverage these ideas in the months ahead. I recommend it to anyone who is or expects to be involved in such a change. I would also recommend it to any tester in an agile development shop. You may not agree with everything in the book, but tells of the future (if not the present) for much of the software testing industry.
Rivik
I like the book's content. What I don't like is its printed format. This book is printed over-sized on standard size 8.5 x 11 inch stock. The printed area is only about 4.25 x 6.5 inches; the font is very small, the margins are very wide, and the title is not printed on the spine. I will buy the book again in a different format -- either hardbound or digital.
Dog_Uoll
The content is excellent, but the printing is so small that the book is very difficult to read. The print takes up about 1/3 of the page so there is large amount of wasted space on the page, why not make the print larger?

If you are thinking about purchasing this book, look at the preview first. It might be easy to read on a Kindle or IPad.
Beazezius
I really enjoyed this book. I became a test manager three months prior to reading it. I wanted to see how a large company ran testing. I was really impressed by the responsibility that Google places on its software engineers for quality. Testing and quality belong to the entire team and not just a few people with the word Quality in their job title.

The end of the book was a surprise. It made me envision a future where quality was just built into the framework for developing applications and not something bolted on at the end. The tools are getting better and the practices are improving to the level that testers can focus on the user experience and not basic correctness.

The hope for testers is that they will be more of a user advocate than a button masher.
WOGY
The book itself is 10X11 inches in size (aprox.). But the printing inside the book is 5x7 and 4 point font! Unless you are able to read with a microscope, this is almost impossible to read! Either the book should be made smaller and save a few trees, or make the print big enough to read!
Uickabrod
Unlike a lot of other books about testing where they simply give you cookbooks of techniques(which are useful, but present an incomplete picture) this book gives you a really insightful birds eye view of how the different test techniques(unit, integration, system and manual) come together to form a cohesive test strategy. The description of all the different job categories at Google(software engineer, software engineer in test, test engineer and test manager) are useful for both large enterprises and smaller shops where the engineers often wear multiple hats. Only suggestion would be to add a bit more about performance/scalability testing in the next version.
Brakora
This book is more about the organization rather than the details of testing software. If you are looking at how to improve how your organization implements its testing process then this is a valuable book. If you are a QA Engineer trying to improve his or her testing skills this book won't help you.
I am not rating the content of the book. I am rating the quality of the physical book. I believe I was shipped a counterfeit book.

This is not an original printing of the book. It seems like someone scanned the book and printed it on the wrong sized paper (including a blurry, stretched cover). From reading other comments it sounds like I am not the only one that has received a bootleg copy of this book.