Ebook How Google Tests Software
Reviewing routine will constantly lead individuals not to pleased reading How Google Tests Software, a publication, ten publication, hundreds e-books, and also much more. One that will certainly make them really feel completely satisfied is completing reviewing this e-book How Google Tests Software as well as getting the notification of guides, then locating the various other next publication to review. It continues an increasing number of. The time to finish reading a book How Google Tests Software will be consistently different depending upon spar time to invest; one instance is this How Google Tests Software
How Google Tests Software
Ebook How Google Tests Software
Do you believe that reading is an important task? Discover your reasons adding is necessary. Checking out a book How Google Tests Software is one component of pleasurable tasks that will make your life top quality better. It is not concerning just what type of e-book How Google Tests Software you check out, it is not only concerning just how numerous books you read, it has to do with the practice. Reviewing routine will certainly be a means to make publication How Google Tests Software as her or his pal. It will certainly no matter if they spend money and spend more publications to finish reading, so does this publication How Google Tests Software
Connected to just what happen in this case, it doesn't suggest that home entertainment will certainly be always fiction. Right here, we will certainly reveal you exactly how a book could offer the enjoyment and factual forms to check out. Guide is How Google Tests Software Do you find out about it? Certainly, this is an extremely widely known publication that is also produced by a popular writer.
Don't bother! Currently, in this modern era, you could get guides from many sources. No should go to the book shops and also walking the city, you could find publication. Below is the website that includes all exceptional publications to collect. You could get it in the soft data as well as use it to check out. Obviously, your tab and computer comes to be excellent device to conserve the book. How Google Tests Software is the best referral to accompany you in this time. It will certainly help you going along with the spare time while holidays.
Visualize that you are resting ignoring something terrific as well as natural; you can hold your gizmo and sit to read How Google Tests Software This is not only about the holidays. This moment will certainly also keep you to constantly raise your expertise and impact to make much better future. When you actually make it possible for to use the time for whatever helpful, your life has been grown completely. It is one of the characteristic that you could get by reading this book. Just a few part of the generous advantages to take by reviewing book.
About the Author
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."
Read more
Product details
Paperback: 320 pages
Publisher: Addison-Wesley Professional; 1 edition (April 2, 2012)
Language: English
ISBN-10: 0321803027
ISBN-13: 978-0321803023
Product Dimensions:
7 x 0.8 x 9.1 inches
Shipping Weight: 1 pounds (View shipping rates and policies)
Average Customer Review:
3.7 out of 5 stars
58 customer reviews
Amazon Best Sellers Rank:
#320,826 in Books (See Top 100 in Books)
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!
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.
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 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.
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.
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.
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.
How Google Tests Software PDF
How Google Tests Software EPub
How Google Tests Software Doc
How Google Tests Software iBooks
How Google Tests Software rtf
How Google Tests Software Mobipocket
How Google Tests Software Kindle
0 komentar:
Posting Komentar