PDF-Download How Google Tests Software, by James A. Whittaker Jason Arbon
Kommen Sie folgen uns jeden Tag genau zu erkennen, was auf einer täglichen Basis aktualisiert Publikationen. Sie verstehen, die Bücher, die wir täglich aktualisiert werden bieten. Neben derzeit, werden wir Ihnen die brandneue Veröffentlichung zur Verfügung stellen, die Empfehlung sein. Sie können How Google Tests Software, By James A. Whittaker Jason Arbon wählen, wie das Buch zur Zeit zu lesen. Warum sollte diese Veröffentlichung sein? Dies ist nur eines der aktuellen Buchsammlungen auf dieser Website zu aktualisieren. Das Buch ist ebenfalls aufgrund der starken Gründen empfohlen, dass viele Menschen zu lieben Verwendung als Analysematerial zu machen.
How Google Tests Software, by James A. Whittaker Jason Arbon
PDF-Download How Google Tests Software, by James A. Whittaker Jason Arbon
Kommen Sie folgen uns jeden Tag zu verstehen, welche Bücher täglich aktualisiert. Sie wissen, Guides, die wir jeden Tag aktualisiert werden bieten. Neben jetzt, werden wir bieten Ihnen sicherlich die brandneue Publikation, die Empfehlung sein. Sie könnten wählen How Google Tests Software, By James A. Whittaker Jason Arbon als Reiseführer zu überprüfen. Warum sollte diese Veröffentlichung sein? Dies ist nur eines der aktuellsten Buchsammlungen auf dieser Website zu aktualisieren. Leitfaden wird zusätzlich als Folge der festen Faktoren vorgeschlagen, dass verschiedene Einzelpersonen wie als Lese Produkt verwenden.
There is without a doubt that publication How Google Tests Software, By James A. Whittaker Jason Arbon will certainly always offer you motivations. Even this is simply a publication How Google Tests Software, By James A. Whittaker Jason Arbon; you could locate numerous styles and types of publications. From captivating to experience to politic, and scientific researches are all supplied. As just what we state, here our company offer those all, from famous authors and publisher in the world. This How Google Tests Software, By James A. Whittaker Jason Arbon is among the collections. Are you interested? Take it currently. Exactly how is the method? Find out more this post!
When someone needs to visit the book establishments, search establishment by shop, rack by shelf, it is quite troublesome. This is why we supply the book compilations in this website. It will certainly reduce you to search guide How Google Tests Software, By James A. Whittaker Jason Arbon as you such as. By searching the title, author, or authors of guide you desire, you can locate them promptly. At home, office, and even in your way can be all ideal place within net connections. If you intend to download the How Google Tests Software, By James A. Whittaker Jason Arbon, it is really easy after that, since now we extend the link to buy and also make offers to download How Google Tests Software, By James A. Whittaker Jason Arbon So very easy!
Interested? Certainly, this is why, we intend you to click the link page to see, and afterwards you can appreciate the book How Google Tests Software, By James A. Whittaker Jason Arbon downloaded and install till finished. You could save the soft file of this How Google Tests Software, By James A. Whittaker Jason Arbon in your gadget. Obviously, you will bring the gadget everywhere, won't you? This is why, each time you have extra time, every single time you could appreciate reading by soft duplicate publication How Google Tests Software, By James A. Whittaker Jason Arbon
Über den Autor und weitere Mitwirkende
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."
Produktinformation
Taschenbuch: 314 Seiten
Verlag: Addison-Wesley Professional; Auflage: 1 (2. April 2012)
Sprache: Englisch
ISBN-10: 0321803027
ISBN-13: 978-0321803023
Größe und/oder Gewicht:
17,8 x 2 x 23,1 cm
Durchschnittliche Kundenbewertung:
4.6 von 5 Sternen
4 Kundenrezensionen
Amazon Bestseller-Rang:
Nr. 15.749 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
I am quite some time around in the Software quality and Testing business, and I have seen and read a lot of books about that topic: Structuring by V-Model, different analysis and design methods, testing as part of a process model and so on.The issue that I had with most, nearly all of them was: Why start testing at the end?Why not prevent defects instead of having to find them? And be made responsible in case, they slipped through.This book is different, like the company.They try to catch a defect before it can make its way to the code, they will rather put off functionality, if it is not properly tested, and so on.All things, that I personally think, make so much sense, and which are not followed by the PMs and Devs of the current business.As I said before, this book is my favorite at least for this year. If not for the decade.It motivated me to get back to programming, to be able to facilitate automatic testing to the dev people to overcome the pain for them. Great!
"Testen" wird in vielen Software-Entwicklungsabteilungen als Aufgabe für fleissige Nörgler angesehen, die nachträglich einem Software-Produkt oder -Projekt Qualität verleihen sollen. Dass das völlig am Thema vorbei geht, ist vielen nicht bewusst.Dieses Buch zeigt, wie man heute Software testen sollte, welche Skills und Rollen man wirklich benötigt, und wie die Denkweise über "Qualitätssicherung und Test" bei der Software-Entwicklung sein sollte.Bei Google produziert man mehr Software mit mehr Entwicklern und mehr Teams als vermutlich sonst irgendwo in einem Unternehmen und hat sich darüber viele Gedanken gemacht und über Jahre das Testen von Software optimiert. Ob Google das heute noch alles so macht (das Buch stammt aus 2012), kann ich nicht beurteilen, aber das Niveau gilt es für jedes Software-Team anzustreben - wobei sich nicht alle Themen in kleineren Software-Projekten anwenden lassen.Wer sollte das lesen?a) Projektleiter, die Software-Entzwicklungsteams leitenb) Software-Entwickler, die Qualität während der konstruktiven Entwicklung in ihr Produkt/Projekt anstrebenc) Test-Engineers und solche die sich vom nörgelnden Klick-Tester weiter entwicklen wollen
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.
The book covers the topic fully, but I would say it is also very interesting for people thinking of applying for a job at google...
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.
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!
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.
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 testingIn 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.
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.
How Google Tests Software, by James A. Whittaker Jason Arbon PDF
How Google Tests Software, by James A. Whittaker Jason Arbon EPub
How Google Tests Software, by James A. Whittaker Jason Arbon Doc
How Google Tests Software, by James A. Whittaker Jason Arbon iBooks
How Google Tests Software, by James A. Whittaker Jason Arbon rtf
How Google Tests Software, by James A. Whittaker Jason Arbon Mobipocket
How Google Tests Software, by James A. Whittaker Jason Arbon Kindle
0 komentar:
Posting Komentar