Download the Art of Software Testing John Wiley 3 Edition

Open Preview

Meet a Problem?

We'd honey your aid. Let us know what's incorrect with this preview of The Art of Software Testing by Glenford J. Myers.

Thanks for telling the states most the problem.

Friend Reviews

To meet what your friends thought of this book, please sign up.

Reader Q&A

Be the commencement to ask a question about The Fine art of Software Testing

Community Reviews

· 231 ratings · 27 reviews

First your review of The Fine art of Software Testing

I accept very mixed feelings about this third edition of what was clearly a landmark book when the first edition came out, over thirty years ago. I beginning read this volume, way back in 1979. It was a godsend and I and relied on it very heavily to encompass the testing topics in what was the commencement undergraduate software engineering form ever taught at the academy I was at. Reading the 3rd edition afterwards putting aside the offset edition for about a decade, I was immediately struck by how much my think I have very mixed feelings nigh this third edition of what was clearly a landmark book when the get-go edition came out, over xxx years agone. I starting time read this book, way back in 1979. It was a godsend and I and relied on it very heavily to cover the testing topics in what was the offset undergraduate software applied science course ever taught at the university I was at. Reading the third edition afterwards putting bated the beginning edition for well-nigh a decade, I was immediately struck past how much my thinking on testing owes to Glenford Myers and to this book in item.

Nonetheless, every bit I continued reading, I became more and more uneasy. In a sense, how do y'all update a classic book? If the book purports to embrace a field, yous update information technology past keeping upward with the field, adding heavily and judiciously pruning stuff which becomes obsolete. This has worked pretty well for Ian Sommerville´s or Roger Pressman´s massive tomes on Software Technology, merely this goes counter to Myer´s whole approach, which aimed at the heart rather than the body of the field and struck thrilling insights into the psychology of testing. The book had its faults, of class, such as Myers dutiful, plodding only ultimately non very convincingly coverage of cause-effect graphing and of college-guild testing, which though striking at offset, slowly collapsed in time.

So, how exercise you update a classic volume. Corey Sandler and Tom Badgett seem to take approached the task gingerly and with great trepidation. They seem to have decided to touch Myer´s original book as lightly as possible, adding some sidebars on the "history" of Fortran, Cobol and PL/one were, then that the mod day reader can wonder why on earth Myers talks well-nigh Mutual statements -a horrible and error-decumbent construct which, to its shame, is still carried around in Fortran-90 even though there are more elegant ways to circumvent it (see for case http://iprc.soest.hawaii.edu/users/fu... for details). Then, I tin imagine Sandler and Badgett huddling together and deciding that, well the capacity on debugging and usability testing take to be redone and the volume volition probably go extinct unless some capacity are added on more gimmicky bug such as usability testing, agile development´s impact on testing and testing web and mobile applications. So the chapter on debugging is duly, if not 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 capacity is the 1 on agile development, which spends a great deal of fourth dimension repetitively telling us what agile development is, but very petty discussing its impact on testing and barely managing to slip in the JUnit tool. The affiliate on web application testing devotes some time to the archetype three-tier architecture (presentation, business and data levels) and goes on to provide a brief and sometimes repetitive overview of testing issues for the iii levels. Still, I fail to understand why the authors failed to tie the ideas on testing the presentation layer more strongly to the chapter on usability and why they skimped and so much on testing the information layer -if in that location is a chapter on usability, I don´t understand why theey failed to add a affiliate on database testing. The chapter on mobile application testing provides a good introduction to the topic but falls into the temptation, as in the chapter on usability, of mentioning so many topics, that the reader is left feeling helpless in the face up of so many shadowy hinted-at complexities. Some of these new capacity have been edited rather carelessly -there is, for example a typo ("donstraints" instead of "constraints") and a spelling error ("shear" for "sheer") in only one page (page 215) and they are not as tightly written as the all-time of Myers.

Even xx years ago, I would have recommended this book without hesitation, now I am non then sure. Some readers volition nevertheless enjoy the key insights from both quondam and new chapters, others will simply yawn and laissez passer them by. Glenford Myers´ book was a landmark, simply like many landmarks, the sheer book of new developments has severely eroded it -however, the perceptive reader should nevertheless be able to appreciate its legacy. I wavered betwixt giving the volume three or 4 stars, but Sandler and Badgett deserve recognition for bravery and Myers still has my gratitude for introducing me to testing, and so four it is.

...more

Jan 29, 2013 Drew rated it liked it

Three stars is pretty skillful for a volume most software testing, since it is the most tedious thing in the world. It hooked me with an early test of my own skills (which I know are bad, merely I didn't realize they were THAT bad) and I am pretty sure I at least read the whole thing. Skillful full general ideas most how to split up up testing in a way that has strong coverage without infinite tests, but information technology didn't do anything to inspire me to test more than. Three stars is pretty practiced for a book about software testing, since it is the virtually boring affair in the world. Information technology hooked me with an early on test of my own skills (which I know are bad, only I didn't realize they were THAT bad) and I am pretty certain I at to the lowest degree read the whole affair. Good general ideas about how to split up testing in a way that has strong coverage without infinite tests, but it didn't do anything to inspire me to test more than. ...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, process, which explains why nigh people find information technology difficult.
When you find an error in a section on a program, the probability of the beingness of another error in that same department is higher than if you hadn't already constitute on error (errors tend to cluster).
به نظ با این کتاب از اینجا آشنا شدم
https://www.yegor256.com/2014/08/22/a...
به نظرم جالب ترین قسمت کتاب این چند تا جمله است.
Testing is the process of executing a programme with the intent of finding errors.
Testing is a destructive, even sadistic, process, which explains why well-nigh people find it difficult.
When you find an error in a department on a program, the probability of the being of another error in that same section is college than if you hadn't already found on mistake (errors tend to cluster).
به نظرم مطالعه فصل دومش فقط جالبه و کافیه.
The Psychology and Economic science of Software Testing
...more

Gave up after they started explaining how to draw horendously complicate diagrams in order to derive test cases in a large test space. Either the work I've washed doesn't require the same level of testing stringency as others or it was just bad. Either way, it just wasn't very applicative at present. Good coverage of terminology in basic blackness-box and white-box testing though. Gave up after they started explaining how to describe horendously complicate diagrams in order to derive examination cases in a big test space. Either the work I've washed doesn't require the same level of testing stringency as others or it was just bad. Either style, it just wasn't very applicable at present. Good coverage of terminology in bones black-box and white-box testing though. ...more

January 09, 2015 Coltin rated it it was ok

I read this comprehend to cover and I sadly am walking away with very trivial. This book feels extremely dated. Especially the section on mobile testing. Information technology'due south very naive and didn't provide any useful information. 2 stars instead of 1 for historical interest on what probably was a good testing volume thirty years ago, but overall I would never recommend. I read this cover to cover and I sadly am walking abroad with very little. This volume feels extremely dated. Particularly the department on mobile testing. Information technology's very naive and didn't provide whatever useful information. 2 stars instead of 1 for historical interest on what probably was a good testing book 30 years ago, only overall I would never recommend. ...more than

Feb 21, 2018 Iuliia rated it liked it

This book was recommended to me by my friend whose expertise I trust but in the end, I was disappointed. I read 2d, not the latest, edition, and thought that it would not thing because the book contains timeless theory that I'll exist able to apply today. Merely my expectations were incorrect and I was able to take away very little. This book was recommended to me by my friend whose expertise I trust merely in the finish, I was disappointed. I read second, not the latest, edition, and thought that information technology would not matter considering the book contains timeless theory that I'll exist able to use today. But my expectations were wrong and I was able to take abroad very fiddling. ...more

Jul 22, 2013 Laura rated it really liked information technology

A expert book for beginners as it states principles and methods of piece of work. Information technology is not enough if you want to realy acquire well-nigh software testing, but information technology'due south a very good starting signal. It is also a overnice reminder for testers with some experience in the field.
A good volume for beginners as it states principles and methods of work. It is non plenty if you want to realy learn about software testing, but it's a very good starting indicate. Information technology is as well a nice reminder for testers with some experience in the field.
...more

This volume is a very good introductory volume about Software testing. I constitute Chapter 4 on Test-Example design the almost informative.

Didn't incorporate as much specific testing info/strategies as I'd hoped. Didn't contain equally much specific testing info/strategies as I'd hoped. ...more

I read the outset edition, and I can run across why it was a classic. Fifty-fifty though the examples, peculiarly the code samples, don't fare that well after 40-some years, the principles are surprisingly applicative today.

I especially appreciate the rigor with which the writer develops bones techniques like boundary-value analysis and equivalence segmentation. In many ways, I feel that the testing that we exercise today does not live up to those high standards, as we seem to struggle with mere lawmaking coverage (statem

I read the beginning edition, and I can see why it was a classic. Even though the examples, especially the code samples, don't fare that well after 40-some years, the principles are surprisingly applicable today.

I peculiarly appreciate the rigor with which the author develops basic techniques like boundary-value assay and equivalence sectionalisation. In many means, I feel that the testing that nosotros do today does not live up to those high standards, as nosotros seem to struggle with mere code coverage (statement coverage), let lone modified-condition/conclusion coverage, except perhaps in rarified sub-fields such as flight-control software.

...more

I just got done reading the first edition.

I comment: In the self-assessment test at the front of the volume, I scored about 11/14, and then establish ii more than questions. (view spoiler)[1. Exercise you have a test instance where the input is not numeric?
2. Practise y'all have a test case where the sum of two numbers results in arithmetic overflow? (hibernate spoiler)]

I just got washed reading the first edition.

I comment: In the cocky-assessment exam at the front end of the book, I scored near eleven/14, and and then found 2 more questions. (view spoiler)[1. Practice yous have a test case where the input is not numeric?
ii. Do you have a test case where the sum of 2 numbers results in arithmetic overflow? (hide spoiler)]

...more

I will non rate this book. As a newbie I got useful information from this book to guide me further and some info that messed with my caput every bit well :D Soo.. no comments, let's come across if this book provided me with plenty cloth to kick-start this new path. I will not charge per unit this book. As a newbie I got useful information from this book to guide me further and some info that messed with my head as well :D Soo.. no comments, let's see if this volume provided me with enough material to kick-start this new path. ...more

Came equally a recommendation from a colleague- chapter one on its ain it astounding.

Jun 16, 2012 Anton rated it liked it

When I was readling the book I thought that it is very tedious, that there are too few specific testing techniques I wanted to learn about. The only chapter that really grabbed my attention was the affiliate about dissimilar types of testing (unit, integration, system and acceptance). Other chapters were not very informative and interesting for me.
Now, having the volume read and looking over what I accept read, I think that my original expectations were too high and were in the incorrect direction. There ar When I was readling the volume I thought that information technology is very dull, that there are too few specific testing techniques I wanted to learn about. The only chapter that really grabbed my attention was the affiliate about different types of testing (unit, integration, organization and acceptance). Other chapters were not very informative and interesting for me.
Now, having the book read and looking over what I have read, I think that my original expectations were also high and were in the incorrect management. There are no specific solutions to test software. At that place are some techniques and common language you tin can use to ameliorate understand each other while testing software. But physical methods are too domain-specific to be generalized. This thought, this high-level overview of techniques and linguistic communication the volume gives us. And that, I think, is a good matter. ...more

Read affiliate 8 on debugging. Very helpful. Summary -- mutual debugging techniques like multiple print statements, breakpoints, and retentivity/variable dumps are less helpful than THINKING. Consecration is gathering the evidence and developing and testing a hypothesis. Deduction is coming up with multiple hypotheses and eliminating incorrect ones. Collect data such as what the mistake was, where and when it does and does non occur, etc. If you spend more than 30 minutes on a problem for a brusque program Read affiliate eight on debugging. Very helpful. Summary -- mutual debugging techniques like multiple print statements, breakpoints, and retentiveness/variable dumps are less helpful than THINKING. Induction is gathering the evidence and developing and testing a hypothesis. Deduction is coming up with multiple hypotheses and eliminating wrong ones. Collect data such as what the fault was, where and when it does and does not occur, etc. If yous spend more than 30 minutes on a problem for a short program, or two hours on a long i, slumber on it. Your brain will work on it while you sleep. ...more

I think that "The Fine art of Software Testing" deserves the title "The archetype guide to software testing". It is a great introduction to master testing techniques and it has a very good chapter on test-example design (the most useful part for me). I plant it very inspiring to perform careful testing. Besides, I appreciate that the volume that was kickoff published in 1979 is updated to contain affiliate on mobile applications testing. I think that "The Art of Software Testing" deserves the title "The classic guide to software testing". It is a not bad introduction to primary testing techniques and it has a very proficient chapter on test-case design (the most useful part for me). I found it very inspiring to perform conscientious testing. Likewise, I appreciate that the volume that was first published in 1979 is updated to contain chapter on mobile applications testing. ...more than

Jan 06, 2016 Juan rated it really liked information technology

It'southward a nice book to introduce someone to the testing concepts and notions, but not to be taken as a definite guide, since some examples and descriptions are not upwards to engagement nor totally clear. However, the main concepts of software testing are presented and explained. Information technology's a nice book to innovate someone to the testing concepts and notions, but non to exist taken as a definite guide, since some examples and descriptions are not up to engagement nor totally clear. However, the main concepts of software testing are presented and explained. ...more

October 13, 2016 Austin rated it really liked it

I remember every aspiring software engineer should read this book.

Jun 02, 2018 Moemen rated it liked information technology

It'south a adept starting for those new to testing field, however it's not well adapted to the Agile environment. It's a good starting for those new to testing field, notwithstanding it's not well adapted to the Agile environment. ...more than