The Art of Software Testing ââ“ Glenford J Myers 3rd Edition Pdf
I accept very mixed feelings about this third edition of what was clearly a landmark book when the starting time edition came out, over 30 years ago. I first read this volume, way back in 1979. It was a godsend and I and relied on it very heavily to comprehend the testing topics in what was the starting time undergraduate software engineering science form always taught at the university I was at. Reading the tertiary edition afterward putting aside the first edition for about a decade, I was immediately struck past how much my thinking on testing owes to Glenford Myers and to this book in item. Nevertheless, as I continued reading, I became more and more uneasy. In a sense, how do yous update a classic book? If the book purports to embrace a field, you update it by keeping up with the field, adding heavily and judiciously pruning stuff which becomes obsolete. This has worked pretty well for Ian Sommerville´due south or Roger Pressman´s massive tomes on Software Technology, only this goes counter to Myer´southward whole approach, which aimed at the center rather than the body of the field and struck thrilling insights into the psychology of testing. The book had its faults, of course, such every bit Myers dutiful, plodding but ultimately non very assuredly coverage of cause-outcome graphing and of higher-guild testing, which though striking at offset, slowly collapsed in time. And so, how do you update a classic book. Corey Sandler and Tom Badgett seem to have approached the chore gingerly and with great trepidation. They seem to have decided to touch on Myer´s original volume equally lightly every bit possible, calculation some sidebars on the "history" of Fortran, Cobol and PL/1 were, so that the modern day reader can wonder why on globe Myers talks about COMMON statements -a horrible and error-prone construct which, to its shame, is nonetheless carried effectually in Fortran-90 fifty-fifty though there are more elegant means to circumvent it (run into for case http://iprc.soest.hawaii.edu/users/fu... for details). Then, I tin can imagine Sandler and Badgett huddling together and deciding that, well the capacity on debugging and usability testing have to be redone and the book volition probably become extinct unless some chapters are added on more contemporary issues such as usability testing, agile development´s bear on on testing and testing web and mobile applications. Then the chapter on debugging is duly, if non inspiringly rewritten, the affiliate on usability is expanded (leaving some really obsolete Myers examples intact) and four new chapters are duly added. The worst of the new chapters is the i on active development, which spends a great deal of fourth dimension repetitively telling usa what agile development is, only very little discussing its impact on testing and barely managing to skid in the JUnit tool. The affiliate on web application testing devotes some time to the classic three-tier architecture (presentation, business concern and data levels) and goes on to provide a brief and sometimes repetitive overview of testing problems for the 3 levels. Still, I fail to understand why the authors failed to tie the ideas on testing the presentation layer more than strongly to the chapter on usability and why they skimped so much on testing the data layer -if there is a affiliate on usability, I don´t understand why theey failed to add a chapter on database testing. The chapter on mobile application testing provides a skillful introduction to the topic only falls into the temptation, as in the chapter on usability, of mentioning then many topics, that the reader is left feeling helpless in the face of and so many shadowy hinted-at complexities. Some of these new chapters take been edited rather carelessly -there is, for example a typo ("donstraints" instead of "constraints") and a spelling error ("shear" for "sheer") in just one page (page 215) and they are not as tightly written as the all-time of Myers. Even 20 years ago, I would have recommended this book without hesitation, now I am not so certain. Some readers will notwithstanding enjoy the fundamental insights from both old and new chapters, others will simply yawn and pass them by. Glenford Myers´ volume was a landmark, but like many landmarks, the sheer volume of new developments has severely eroded it -yet, the perceptive reader should still be able to appreciate its legacy. I wavered between giving the book iii or 4 stars, only Sandler and Badgett deserve recognition for bravery and Myers still has my gratitude for introducing me to testing, so four it is.
Three stars is pretty expert for a book virtually software testing, since it is the nearly boring affair in the earth. It hooked me with an early test of my own skills (which I know are bad, but I didn't realize they were THAT bad) and I am pretty certain I at least read the whole affair. Good general ideas about how to carve up upwardly testing in a way that has strong coverage without space tests, merely it didn't do annihilation to inspire me to examination more.
با این کتاب از اینجا آشنا شدم
https://www.yegor256.com/2014/08/22/a...
به نظرم جالب ترین قسمت کتاب این چند تا جمله است.
Testing is the process of executing a program with the intent of finding errors.
Testing is a destructive, even sadistic, procedure, which explains why most people detect information technology hard.
When you notice an fault in a section on a program, the probability of the existence of another error in that same section is higher than if you hadn't already found on error (errors tend to cluster).
به نظرم مطالعه فصل دومش فقط جالبه و کافیه.
The Psychology and Economics of Software Testing
Gave up after they started explaining how to draw horendously complicate diagrams in order to derive examination cases in a large test space. Either the work I've done doesn't require the same level of testing stringency as others or it was just bad. Either way, information technology but wasn't very applicative at present. Expert coverage of terminology in basic black-box and white-box testing though.
I read this cover to cover and I sadly am walking abroad with very picayune. This book feels extremely dated. Peculiarly the section on mobile testing. It's very naive and didn't provide any useful information. 2 stars instead of 1 for historical interest on what probably was a skillful testing volume 30 years ago, but overall I would never recommend.
This book was recommended to me by my friend whose expertise I trust merely in the end, I was disappointed. I read second, not the latest, edition, and thought that it would non affair because the volume contains timeless theory that I'll exist able to apply today. Just my expectations were wrong and I was able to take away very little.
A good volume for beginners equally it states principles and methods of work. It is not enough if y'all want to realy learn virtually software testing, merely it'south a very proficient starting point. It is also a nice reminder for testers with some experience in the field.
Didn't comprise as much specific testing info/strategies as I'd hoped.
This book is a very expert introductory book about Software testing. I plant Chapter 4 on Test-Case design the most informative.
Displaying 1 - 10 of 26 reviews
Source: https://www.goodreads.com/book/show/877789.The_Art_of_Software_Testing
0 Response to "The Art of Software Testing ââ“ Glenford J Myers 3rd Edition Pdf"
Post a Comment