Identifiez-vous pour activer la commande 1-Click.
Plus de choix
Vous l'avez déjà ? Vendez votre exemplaire ici
Désolé, cet article n'est pas disponible en
Image non disponible pour la
couleur :
Image non disponible

Dites-le à l'éditeur :
J'aimerais lire ce livre sur Kindle !

Vous n'avez pas encore de Kindle ? Achetez-le ici ou téléchargez une application de lecture gratuite.

JUnit in Action [Anglais] [Broché]

Vincent Massol

Prix : EUR 31,17 LIVRAISON GRATUITE En savoir plus.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Temporairement en rupture de stock.
Commandez maintenant et nous vous livrerons cet article lorsqu'il sera disponible. Nous vous enverrons un e-mail avec une date d'estimation de livraison dès que nous aurons plus d'informations. Cet article ne vous sera facturé qu'au moment de son expédition.
Expédié et vendu par Amazon. Emballage cadeau disponible.
Il y a une édition plus récente de cet article:
JUnit in Action JUnit in Action
EUR 26,89
En stock.

Description de l'ouvrage

13 novembre 2003

JUnit in Action is an example-driven, how-to book about unit testing Java applications (including J2EE applications) using the JUnit framework and its extensions. Intended readers are software architects, developers, testing teams, development managers, Extreme Programmers, or anyone practicing any Agile Methodology.

JUnit in Action is about solving tough real-world problems such as unit testing legacy applications, writing real tests for real objects, automating tests, testing in isolation, unit testing J2EE and database applications, and more.

Offres spéciales et liens associés

Descriptions du produit

Biographie de l'auteur

Vincent Massol is the creator of the Jakarta Cactus framework. He is also an active member of the Maven, Gump, Struts and MockObjects development teams. After having spent 4 years as a Technical Architect on several major projects  (mostly J2EE), Vincent is now the co-founder and CTO of Pivolis, a company specialized in applying Agile Methodologies to Offshore Software Development. Consultant and lecturer during the day and open source developer at night, Vincent dreams of the time when he will be wise enough to devote all his time to his wife and two children. Vincent currently lives in Paris, France.

Ted Husted is the lead author of the best-selling Struts in Action, an active  member of the Struts development team, and manager of the JGuru Struts Forum. As a consultant and lecturer, Ted has worked with Java development teams throughout the United States. Ted's most recent development project uses Test-Driven Design throughout and is available as open source [wqdata]. Ted lives in Fairport NY with his wife, two children, four computers, and anaging cat.

Détails sur le produit

En savoir plus sur les auteurs

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

Vendre une version numérique de ce livre dans la boutique Kindle.

Si vous êtes un éditeur ou un auteur et que vous disposez des droits numériques sur un livre, vous pouvez vendre la version numérique du livre dans notre boutique Kindle. En savoir plus

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: 4.4 étoiles sur 5  21 commentaires
22 internautes sur 22 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 the first edition was better 20 août 2010
Par Jeanne Boyarsky - Publié sur Amazon.com
I truly enjoyed reading the first edition of "JUnit in Action" and was somewhat disappointed by the second edition. It wasn't even that the second edition was bad. It's that my expectations were too high from the first edition.

I think there were too many authors on the book. The different styles were apparent which is awkward in a book. The cover says the book covers JUnit 4.8 while the contents of the book are JUnit 4.6. (This one is probably marketing's fault, but it stands out extra on a book about quality.)

I also think the scope of the book was too large. Many things are covered, but not enough things are covered well. I expect a book titled "JUnit in Action" to cover the core of JUnit well. While most things were mentioned, there were only 3 pages on Hamcrest matchers. I felt other core concepts were breezed through and not enough space was spent on the fundamentals. The first edition had more pages on core JUnit and there was less to cover then!

I was also surprised not to see Mockito mentioned in the mock testing section or Emma in the coverage section. Not featured, mind you. Just mentioned. And finally, I found one factual error that I consider significant because it is a fallacy. I posted it in the Manning forum 8/3 and haven't received a reply. Nor have many people who posted since May or beyond. Why is there a forum if nobody reads it?

Many things were done well - examples, best practices, available tools. I just had the bar so high from the previous edition that I was let down.

If you already own the first edition or are familiar with what is out there, you don't need this book. If you've never done anything in JUnit, it is still useful. Just remember that the order unit tests are run is not guaranteed!

Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of JavaRanch.
22 internautes sur 22 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 A quality and indepth view into the world of Unit Testing 20 novembre 2003
Par Dion G Almaer - Publié sur Amazon.com
When I first started to read JUnit in Action, I was hoping that it wouldn't be a tutorial on the open source tool JUnit. I am glad to say that it is much more. I think the book's name could really be "Testing in Practice". Sure, JUnit is covered in a lot of detail, but so are other tools such as:
- Integration with: Ant, Maven, and Eclipse
- Mock Objects (via both EasyMock and DynaMock)
- Cactus for testing in a container
- And other small helper tools (nice ant tasks, etc.)
What made me really enjoy this book is the way it is written, coupled with the practical look at the many technologies involved in testing. It is a fresh read, that doesn't get bogged down. The book flows really well, giving you best practices throughout. They don't just say "Do X", they actually show you where these best practices come from as they refactor their own code. You are really aware that these authors know their stuff, and are drawing from a lot of experience (compared to the online FAQs).
14 internautes sur 14 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 A joy to read but... 20 février 2005
Par Riccardo Audano - Publié sur Amazon.com
Format:Broché|Achat authentifié par Amazon
This book is required reading for any professional Java developer. Even if you are not convinced of the benefits of test driven development and unit testing you owe it to yourself to check what this is all about. This book will serve as a very hands-on introduction to a lot of APIs, libraries and techniques in the field of unit and integration testing. My only complaint is that it tries to cover too many subjects in too little space. The introductory part on JUnit is superb. I found the treatment of Cactus, surprisingly, too superficial (Vincent Massol is the cactus creator) : the author makes you first (after a brief interlude with Jetty) run the cactus test using Maven, and that would be ok with me if he gave a through introduction to this tool, but instead all you get is a "run the tests typing maven cactus:test". Now this kind of monkey work is not what an intelligent developer loves to do.. and besides when things go even slightly wrong (and you know they will...) you are left clueless. You also get a chance to run cactus tests with ant but the treatment is not general enough to give you a solid understanding of this procedure. Anyhow after reading this book you will be much more competent on software development best practice and testing, but probably wondering if, having to learn and employ all these tools and APIs, unit testing is still useful or is monstrously transforming into a heavy and complex part of your application...
14 internautes sur 16 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Thorough and concise work on JUnit 25 février 2004
Par Jack D. Herrington - Publié sur Amazon.com
This is a strong book on a worthy topic. It's short but that doesn't stop it from covering the topic well. The authors just stay on track and cover the required material in a brief and balanced manner.
On the down side there could have been more context about JUnit and it's alternatives. The first chapter covers this somewhat but after that it is JUnit all the way.
On the upside, the book is well written and edited. It is concise and sometimes witty but not to the level of going off track.
The interesting chapters:
Chapter one introduces JUnit and shows some alternatives, mainly doing tests by hand.
Chapter two covers JUnit completely in detail. Which is almost a bit too much too fast and I found myself a little lost in the detail. It could stand to be broken up a little.
Chapter four is an excellent introduction to test driven development. This section alone is almost worth the price of the book.
Chapter five covers integrating JUnit into existing tools like Ant and Eclipse.
The second part then applies JUnit to each of a number of different types of code, including web pages, tag libraries, data access, etc. This is the heart of the matter and it's done very well. This connects the code you have to the JUnit test framework step by step. It's very well done.
If you are using JUnit or are interested in test driven development in Java this is a fantastic book and is well worth the money.
(Full disclosure: I am a Manning author but I in no way allow that to effect my reviews.)
5 internautes sur 5 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 An ACTION packed thriller with JUnit. Must Read 22 avril 2006
Par Ganeshji Marwaha - Publié sur Amazon.com
First things first --> Test Driven(First) Development (TDD) is a *beaten to death* buzz phrase in the IT industry today. There are various proponents and opponents to this agile concept. Let me tell you that this book is neither a proponent nor an opponent to TDD, it just teaches you plain vanila unit-testing and how it will make you develop quality solutions.

Won't you agree if i say that we see or hear a few of the following during our typical work day.

1. JUnit, HttpUnit, DbUnit etc

2. Mock/Stub testing strategy

3. Repeatable tests, Continuous Integration

4. Innovative Testing frameworks like EasyMock, TestNG, Cactus etc

5. Designing and writing code for testability

Often, when we try to find out what exactly they are and how they are used in real projects, we are left with uninspiring documentation(if there is one) or we are left with a plethora of frameworks that do overlapping tasks. Without knowing *what, when and why's* of unit testing, we thrash it at the end of the day.

This book is an excellent resource in that it addresses the above questions and the questions that follow really well in a developer friendly manner.

1. Why to unit-test code? What advantages do you get by doing so? --> Quality, Confidence, Merciless Refactoring

2. What are the different types of tests that a software needs and how does unit testing fit into the overall picture? --> Unit, Integration, Functional and Acceptance tests

3. What is JUnit and how it fits into the unit-testing phase of our development process? --> Makes unit-testing a breeze

4. What tasks are not do-able with JUnit and how other frameworks and JUnit extensions address these issues? --> Cactus, EasyMock, HttpUnit, DbUnit etc

5. What are the different testing strategies that are available and when to use them? --> Stub, Mock, In-Container

6. What are the problems that you will encounter while unit testing and how to overcome them? --> Demotivation,

7. What are the different reasons that you will find to not do unit testing? Why and how to overcome them? --> Time Pressure, Not Applicable in my scenaro etc

8. How to test different types of artefacts? --> POJOs, Servlets, JSPs, Taglibs, Database Access, EJBs

9. How unit testing can be made fun? --> Profiling, metrics

10. All of these in a simple yet effective case study. --> Adminstration App.

There are a few *nice to have's* that this book missed:

1. Though it covers a lot of detail, i think the authors tried to cover too much ground in 350+ pages. Cactus was covered, but very superficially, particularly in the TestRunner area. I would expect greater detail in that area, because that is the most diffuclt part of cactus.

2. It would have been better if the authors concentrated more on *what to test* after the initial *how to test* chapters. I mean, since the authors are expert in this arena, it would have been better if they identified a few patterns on what gets commonly tested and put it forward to us. That would have been very useful.

Overall, this is a very well written book. The authors are not only technical experts, they are good writers as well. If you are even vaguely interested in trying out unit testing for your projects, you owe yourself to try this book and get enlightened.

Any program feature without an automated test simply doesn't exist. -- Kent Beck
Ces commentaires ont-ils été utiles ?   Dites-le-nous

Discussions entre clients

Le forum concernant ce produit
Discussion Réponses Message le plus récent
Pas de discussions pour l'instant

Posez des questions, partagez votre opinion, gagnez en compréhension
Démarrer une nouvelle discussion
Première publication:
Aller s'identifier

Rechercher parmi les discussions des clients
Rechercher dans toutes les discussions Amazon

Rechercher des articles similaires par rubrique


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