|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
How Google Tests Software
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| |||||||||||||||
Wird oft zusammen gekauft
Produktinformation
|
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von James A. Whittaker auf Amazon
› Besuchen Sie die Seite von James A. Whittaker auf Amazon
Produktbeschreibungen
Kurzbeschreibung
Pioneering the Future of Software Test Do you need to get it right, too? Then, learn from Google. 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 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!
Über den Autor
James Whittaker is an engineering director at Google and has been responsible for testing Chrome, maps, and Google web apps. He used to work for Microsoft and was a professor before that. James is one of the best-known names in testing the world over. Jason Arbon is a test engineer at Google and has been responsible for testing Google Desktop, Chrome, and Chrome OS. He also served as development lead for an array of open-source test tools and personalization experiments. He worked at Microsoft prior to joining Google. 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. He converted to a software engineer in 2010 and leads development of Google+ APIs. He also worked at Microsoft prior to joining Google."
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
Format:Taschenbuch|Von Amazon bestätigter Kauf
Ein Überblick über Googles Testorganisation. Zumindest die, die Google bis vor kurzer Zeit hatte. Denn am Ende des Buches wird erwähnt, dass Google inzwischen in eine andere Richtung geht.
Testmethoden oder Testwerkzeuge sind nicht das Thema des Buches und werden deshalb höchstens erwähnt. Eine Ausnahme ist ACC (attributes, components, capabilities), dem die Autoren einige Seiten spendiert haben.
Testmethoden oder Testwerkzeuge sind nicht das Thema des Buches und werden deshalb höchstens erwähnt. Eine Ausnahme ist ACC (attributes, components, capabilities), dem die Autoren einige Seiten spendiert haben.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
9 Rezensionen
2 von 2 Kunden fanden die folgende Rezension hilfreich
Very educational and very entertaining!!!
11. Mai 2012
Format:Taschenbuch
As I read the beginning of this book I was thinking to myself that the story being told of a giant like Google seems just a little too good to be true, but I will trust what they are saying about the atmosphere. Giant companies have never impressed me. They take on their own life and the individual is usually lost in the shuffle.
When I was near the end of the book is when I found out James Whittaker quit Google. In his blog "Why I left Google" he describes what I had envisioned Google to be. It sounds like Google has made some bad decisions to compete with Facebook, just like Microsoft has made some horrible decisions to compete with Apple.
That said, this book is still a great read. It talks about the events that James calls the old Google and I highly recommend reading it.
After the book gives an introduction to what testing at Google is, it has a chapter on each role in their testing world. Each chapter goes into great detail about the tools they use, the different test sizes, coding practices, team structure, process, bug attributes, workflow, and much more. There are also ton of really interesting interviews scattered throughout the book. I found these really entertaining.
The book chapters include Introduction to Google Software Testing , The Software Engineer in Test , The Test Engineer , The Test Engineering Manager , and Improving How Google Tests Software. It also includes three appendices Chrome OS Test Plan , Test Tours for Chrome , and Blog Posts on Tools and Code.
This book is now part of the orientation of new employees at Google, so if you plan on interviewing with them, it may be a good idea to read it in advance.
Testing can become a major pain point on any decent size project. If done wrong, it can be a huge bottleneck and a source of pain, instead of being a relief and productivity gain. This book has tons of advice on how to avoid going off the rails with testing.
This book isn't only for testers. The Software Engineer in Test is a developer focused on testability and test infrastructure. The chapter that covers The Software Engineer in Test is great for all developers to read.
IT Managers, CIOs, Software Architects, and Enterprise Architects should definitely read this book. It is guaranteed to give you ideas and advice that you can use to improve testing in your organization.
Over all I found this book very educational and very entertaining!!!
When I was near the end of the book is when I found out James Whittaker quit Google. In his blog "Why I left Google" he describes what I had envisioned Google to be. It sounds like Google has made some bad decisions to compete with Facebook, just like Microsoft has made some horrible decisions to compete with Apple.
That said, this book is still a great read. It talks about the events that James calls the old Google and I highly recommend reading it.
After the book gives an introduction to what testing at Google is, it has a chapter on each role in their testing world. Each chapter goes into great detail about the tools they use, the different test sizes, coding practices, team structure, process, bug attributes, workflow, and much more. There are also ton of really interesting interviews scattered throughout the book. I found these really entertaining.
The book chapters include Introduction to Google Software Testing , The Software Engineer in Test , The Test Engineer , The Test Engineering Manager , and Improving How Google Tests Software. It also includes three appendices Chrome OS Test Plan , Test Tours for Chrome , and Blog Posts on Tools and Code.
This book is now part of the orientation of new employees at Google, so if you plan on interviewing with them, it may be a good idea to read it in advance.
Testing can become a major pain point on any decent size project. If done wrong, it can be a huge bottleneck and a source of pain, instead of being a relief and productivity gain. This book has tons of advice on how to avoid going off the rails with testing.
This book isn't only for testers. The Software Engineer in Test is a developer focused on testability and test infrastructure. The chapter that covers The Software Engineer in Test is great for all developers to read.
IT Managers, CIOs, Software Architects, and Enterprise Architects should definitely read this book. It is guaranteed to give you ideas and advice that you can use to improve testing in your organization.
Over all I found this book very educational and very entertaining!!!
2 von 2 Kunden fanden die folgende Rezension hilfreich
Nice one
9. Mai 2012
Format:Taschenbuch
Great book on software testing. Even though this book describes the different test roles at Google, I guess everyone spftware engineer could learn something from these guys. After all, not just the testers are responsible for the overall quality of a product, but the entire team. It's also interesting to learn how Google engineers have solved their different problems related to scale and performance.
1 von 1 Kunden fanden die folgende Rezension hilfreich
A nice alternatives to the traditional
4. Mai 2012
Format:Kindle Edition|Von Amazon bestätigter Kauf
Excellent book, is easy to read and well written, In my opinion there are a few minor issues but not worth removing a star.
This book shows an excellent example of alternative thinking... can`t use the traditional way of software testing... ok, then .. lets make our own way. Keeping the basics but making the testing proccess evolve.
This book shows an excellent example of alternative thinking... can`t use the traditional way of software testing... ok, then .. lets make our own way. Keeping the basics but making the testing proccess evolve.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
