Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir les 2 images

The Art of Unit Testing: with Examples in .NET (Anglais) Broché – 11 juin 2009

Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon Neuf à partir de Occasion à partir de
"Veuillez réessayer"
EUR 71,84 EUR 15,38

Il y a une édition plus récente de cet article:

The Art of Unit Testing
EUR 38,45
En stock.

A court d'idées pour Noël ?

Offres spéciales et liens associés

Les clients ayant acheté cet article ont également acheté

Descriptions du produit

Présentation de l'éditeur


Here’s what Michael Feathers, an Agile rock star in his own right, has to say

about The Art of Unit Testing : “This is the best all around introduction to unit

testing on the market today.”


The Art of Unit Testing guides the reader on the journey from beginner to master

in the subtle art of unit testing. Based on expert author Roy Osherove’s

real-world development experiences, this book shows developers how to make

sure the code that they write actually works as expected, and how to make these

verifications as automated as possible. Not only that, the book shows techniques

that help to make sure that tests are maintainable, readable, and test the right

thing over time.

The author establishes five rules for good unit tests built upon the three major

principles that any good test be maintainable, trustworthy, and readable. Clear

sections present established best practices, and the book also provides clear guidance

on what to test and where to start testing in a legacy code project.

Unlike other books on this topic, this book trades theory for real-world examples.

It’s designed so that a working developer can start writing better unit tests

now. Unlike most Unit Testing and TDD books, most examples are in C#

on the .NET platform.


• Introduction to unit testing and the basics of writing real-world unit tests

• Best practices for writing maintainable, trustworthy, readable tests

• Author Roy Osherove is highly visible and extremely well-known in this field


Agile principles like unit testing have found their way more slowly into the

Microsoft community than they have in Java. This book presents the well-honed

practices common in the Java world using examples in C#.

Biographie de l'auteur

For over a decade,

Roy Osherove has been a developer, lead, manager, and architect.

Roy speaks at international conferences such as TechEd, DevTeach, JAOO,

and DevDays about subjects relating to Agile development, unit testing and testdriven

development. He’s the founder of the Agile Israel User group and consults

and trains teams around the world.

Détails sur le produit

En savoir plus sur l'auteur

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Dans ce livre (En savoir plus)
Parcourir les pages échantillon
Couverture | Copyright | Table des matières | Extrait | Index | Quatrième de couverture
Rechercher dans ce livre:

Quels sont les autres articles que les clients achètent après avoir regardé cet article?

Commentaires en ligne

Il n'y a pas encore de commentaires clients sur Amazon.fr
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoiles

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 47 commentaires
29 internautes sur 31 ont trouvé ce commentaire utile 
Approachable Yet Thorough 9 juin 2009
Par Mark Seemann - Publié sur Amazon.com
Format: Broché
This book covers unit testing in .NET from a pragmatic, yet thourough and passionate, perspective. In brief, it covers many important dimensions of unit testing from simple "hello world" tests over the use of Stubs and Mocks to how you write maintainable test code. It also covers organizational topics such as how you introduce unit testing in an organization and how to do code reviews of tests.

Although unit testing has become somewhat synonymous with Agile practices, such as Test-Driven Development (TDD), the book never assumes that you will be using TDD. It is valuable wether you write your tests before or after your code.

Roy Osherove clearly has a lot of experience with unit testing, and he willingly shares so we can learn from his mistakes and successes. As a long-term practitioner of TDD myself, I can vouch for most of the advice imparted by this book: It is based on established patterns and best practices that the unit testing community have arrived at through years of experimentation.

Being the anal-retentive perfectionist that I am, I would have liked to see the book adopt the Pattern Language of xUnit Test Patterns: Refactoring Test Code (Addison-Wesley Signature Series), but at least the guidance of those two books are very much in harmony, even if the terminology differs.

In summary, you can say that this book is a very readable and useful introduction to unit testing. If you are a beginner to intermediate unit test developer, you should definitely read this book - and then, as you become more advanced, you should still read xUnit Test Patterns :)
18 internautes sur 20 ont trouvé ce commentaire utile 
Best book on Unit Testing - Ever 6 juillet 2009
Par BOO - Publié sur Amazon.com
Format: Broché
This book is not an evolutionary book to other unit testing books out there; it's revolutionary.

First of all it's not a thinly disguised book trying to sell you on TDD (as some unit testing books that I've read are), but rather it's a book that truly lives up to it's title - the art of unit testing.

Secondly, the discussions and examples in the book take real world considerations in mind. These are not simple contrite 'Hello World' tests, or 'perfect world' sets of code. It discuss' writing tests on both green and brown field applications.

A third aspect that is truly helpful is that there is an entire section for dealing with implementing unit testing in an organization and the politics you might face while doing so. Because the book isn't biased towards a particular software discipline, tool, or language, but on the 'art' of unit testing, these are tips and tricks you can take with you anywhere.

If you found books like 'The Pragmatic Programmer' or 'The Inmates are Running the Asylum' getting you revved up to write better software, then this book will drive you to a whole new level of unit testing.

I've been doing unit testing for several years now, but it wasn't until after I read this book, that it no longer was a chore that I checked off my 'TODO' list.
9 internautes sur 9 ont trouvé ce commentaire utile 
Succinct, Pragmatic and Actionable 19 juillet 2009
Par R. Garibay - Publié sur Amazon.com
Format: Broché
The Art of Unit Testing: with Examples in .NET

In short, if you want a tactical book on unit testing that distills the passion and love of an expert practitioner into a very readable yet reference-friendly text on unit testing, this is it.

If you are new to unit testing or TDD, this book will demystify the practices, tools and techniques that would otherwise take years and lots of frustration to get right.

If you are an experienced practitioner of unit testing and TDD, and are already practicing SOLID, TOOD, and BDD not just as a flavor of the week but as a way of life, this book will provide unambiguous insight into different approaches that will help you refine your existing techniques or at a minimum, validate your approach which is always valuable to any developer who has an opportunity to review his/her techniques with a seasoned master. This book will afford you that opportunity.

While the book cites excellent references for TDD and design patterns, if there is one thing that I thought was missing was a narrative- even if by way of an appendix- that ties all of the techniques covered together in an example of building the example Logger component using TDD. I understand that this book is not about TDD, but at the same time, that's like a book on scuba equipment that teaches you precisely how to pressurize your CO2 tank, keep your mask from fogging up and care and maintenance of your scuba suit not being about scuba diving.

That said, knowing Roy, it must have been painful to resist a detailed examination on TDD, but, for this book to be effective, it had to be relatively short, to the point and most of all pragmatic for it to succeed at filling the void on the topic of unit testing techniques and practices. To that end, Roy hits the mark very elegantly without being pretentious, catering to those who test first, test last or don't (yet) test at all. While I would love for everyone to pick this book up and start doing TDD today, even if you aren't yet convinced on TDD, applying these techniques to writing code that is testable, and learning how to test the right things will be an instant asset to your product, your team and your organization.
8 internautes sur 8 ont trouvé ce commentaire utile 
Best Unit Testing Book i have read to date 17 mars 2010
Par ncage - Publié sur Amazon.com
Format: Broché
Ok yes i didn't rate it at 5 stars but i think its definitely a book everyone should have on their shelf. A lot of books i read go up for sale after i'm done this won't happen to this book. Its a keeper. Don't kid yourself. Unit testing is hard especially if your working on a system that wasn't designed / architected for unit testing. This book allowed me to "start" implementing unit testing in our internal app that i thought in the past would be impossible to add unit test to. Roy does a lot show you how to break down a system (dependencies mainly) to be able to unit test it. He has great standards to start from (naming, construction, ect...). He also adds enough info about TDD (Test-Driven Development) to show the advantages but doesn't turn into a testing zealot.

That being said the book isn't perfect (reason for 4 instead of 5 stars). First he talks very briefly in the early chapters (forgot which one) about Inversion of Control containers (IOC). He talks about IOC somewhere around where he is talking about constructor injection. He then goes on to say that IOC are beyond the scope of the book. I definitely disagree with this and think a good amount of space in the book (maybe a chapter or part of a chapter) should have been taken discussing the principles of IOC and where/why/how to use it. Its an integral part of constructor injection. If its beyond the scope of a unit testing book then where does it belong? IOC is beyond the scope of the book yet a discussion on a productivity tool (resharper) is (which i have to say i didn't mind because i found it interesting)? I just think this is a big omission in this book and is the main reason for the (-1 star) and not my 2nd point i'm about to make.

Ok the 2nd thing is the author works for TypeMock. He finally tells you that in later chapters. He seems to push Typemock a wee to much i think. Yes TypeMock is definitely the best mocking framework out there. It will allow you to mock things that you generally couldn't mock with other frameworks (Static/Shared methods) but after looking at the cost its more than a little expensive. It would have helped us greatly but the licensing cost are unreasonable (especially when you compare it to the other frameworks...FREE). Anyways, back to the topic at hand. I think the author seems to push it a little to much in the book though i will have to give it to him for using RhinoMock (free) for almost all his examples in the book.
4 internautes sur 4 ont trouvé ce commentaire utile 
Great jumpstart to improving your unit tests... in any language 9 juin 2012
Par Matthew Jessick - Publié sur Amazon.com
Format: Broché
I work on a 75 programmer project in C++ and this book has had a noticible effect on the quality of our unit tests. I read the book after one year of unit testing experience. I was able to immediately clean up many of my own bad practices by taking advantage of the many years of experience related by the author in this book.

We bought half a dozen more copies for the team and you can almost see the rolling waves of more useful and maintainable unit tests fanning out wherever those books travel.

The .NET aspects are not intrusive. This book is very useful for anyone who writes unit tests in any language, but doesn't yet have 10 years of experience to know how best to do so.
Ces commentaires ont-ils été utiles ? Dites-le-nous


Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?