Actuellement indisponible.
Nous ne savons pas quand cet article sera de nouveau approvisionné ni s'il le sera.
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 cette image

Test-Driven development by Example (Livre en allemand) (Anglais) Broché – 1 décembre 2004


Voir les 2 formats et éditions Masquer les autres formats et éditions
Prix Amazon Neuf à partir de Occasion à partir de
Broché, 1 décembre 2004

Devenez auteur avec Kindle Direct Publishing Devenez auteur avec Kindle Direct Publishing

--Ce texte fait référence à l'édition Broché.

Offres spéciales et liens associés


Descriptions du produit

Quatrième de couverture

Clean code that works--now. This is the seeming contradiction that lies behind much of the pain of programming. Test-driven development replies to this contradiction with a paradox--test the program before you write it.

A new idea? Not at all. Since the dawn of computing, programmers have been specifying the inputs and outputs before programming precisely. Test-driven development takes this age-old idea, mixes it with modern languages and programming environments, and cooks up a tasty stew guaranteed to satisfy your appetite for clean code that works--now.

Developers face complex programming challenges every day, yet they are not always readily prepared to determine the best solution. More often than not, such difficult projects generate a great deal of stress and bad code. To garner the strength and courage needed to surmount seemingly Herculean tasks, programmers should look to test-driven development (TDD), a proven set of techniques that encourage simple designs and test suites that inspire confidence.

By driving development with automated tests and then eliminating duplication, any developer can write reliable, bug-free code no matter what its level of complexity. Moreover, TDD encourages programmers to learn quickly, communicate more clearly, and seek out constructive feedback.

Readers will learn to:

  • Solve complicated tasks, beginning with the simple and proceeding to the more complex.
  • Write automated tests before coding.
  • Grow a design organically by refactoring to add design decisions one at a time.
  • Create tests for more complicated logic, including reflection and exceptions.
  • Use patterns to decide what tests to write.
  • Create tests using xUnit, the architecture at the heart of many programmer-oriented testing tools.

    This book follows two TDD projects from start to finish, illustrating techniques programmers can use to easily and dramatically increase the quality of their work. The examples are followed by references to the featured TDD patterns and refactorings. With its emphasis on agile methods and fast development strategies, Test-Driven Development is sure to inspire readers to embrace these under-utilized but powerful techniques.



    0321146530B10172002
  • --Ce texte fait référence à l'édition Broché .

    Biographie de l'auteur

    Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.



    --Ce texte fait référence à l'édition Broché .


    Détails sur le produit

    • Broché
    • Editeur : Pearson (1 décembre 2004)
    • Langue : Anglais
    • ISBN-10: 8131715957
    • ISBN-13: 978-8131715956
    • Dimensions du produit: 24,2 x 18,2 x 1,2 cm
    • Moyenne des commentaires client : 4.0 étoiles sur 5  Voir tous les commentaires (4 commentaires client)
    • Table des matières complète
    •  Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?


    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 et rechercher une autre édition de ce livre.
    Parcourir les pages échantillon
    Couverture | Copyright | Table des matières | Extrait | Index
    Rechercher dans ce livre:

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

    Commentaires en ligne

    4.0 étoiles sur 5
    5 étoiles
    2
    4 étoiles
    0
    3 étoiles
    2
    2 étoiles
    0
    1 étoiles
    0
    Voir les 4 commentaires client
    Partagez votre opinion avec les autres clients

    Commentaires client les plus utiles

    9 internautes sur 10 ont trouvé ce commentaire utile  Par "stephanetavera" le 5 février 2005
    Format: Broché
    Vous pensiez satisfaire l'item 'testing' des pratiques de eXtreme Programming dans vos développements ?
    Ce livre devrait encore vous surprendre, avec une approche radicale de la mise en oeuvre des tests unitaires.
    Le premier chapitre comporte des exemples qui feront bondir les 'seniors'. Mais c'est pour mieux faire passer ce changement de mentalités qui inverse l'ordre classique design puis tests.
    Ouvrage synthétique et limpide : à lire et à mettre en pratique dès que possible !
    Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
    Merci pour votre commentaire. Si ce commentaire est inapproprié, dites-le nous.
    Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
    2 internautes sur 2 ont trouvé ce commentaire utile  Par T. Hakim le 30 novembre 2010
    Format: Broché Achat vérifié
    Test-Driven Development de Kent Beck est une référence dans le TDD. Pragmatique et clair, je vous recommande clairement ce bouquin d'autant plus qu'il n'y a pas vraiment d'équivalent français.
    Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
    Merci pour votre commentaire. Si ce commentaire est inapproprié, dites-le nous.
    Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
    1 internautes sur 1 ont trouvé ce commentaire utile  Par Fukei le 23 mars 2013
    Format: Broché
    Ouvrage "séminal", comme on dit en anglais, qui présente de manière pratique l'approche du développement piloté par les tests. Sauf que depuis l'écriture du livre, cette pratique a eu le temps de s'implanter dans les esprits, à défaut de s'implanter dans les projets. Il n'est donc pas certain que le professionnel de l'informatique y apprendra quoi que ce soit de nouveau.

    En conclusion, un livre à recommander au profane uniquement.
    Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
    Merci pour votre commentaire. Si ce commentaire est inapproprié, dites-le nous.
    Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
    Format: Broché
    Certes, ce livre est le seul sérieux sur le sujet, mais j'ai cependant été un peu déçu par sa lecture. Le TDD est clairement un problème de pratique rigoureuse, je n'ai pas en l'impression d'apprendre énormément de chose grâce à ce livre.
    Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
    Merci pour votre commentaire. Si ce commentaire est inapproprié, dites-le nous.
    Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer

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

    Amazon.com: 63 commentaires
    46 internautes sur 47 ont trouvé ce commentaire utile 
    Fail, Run, Run Clean 4 février 2003
    Par Thomas Koenig - Publié sur Amazon.com
    Format: Broché
    The are a small number of writers who can teach programming skills effectively. Kent Beck is one of them. There are a small set of practices that you can adopt on your own that will have an clearly observable impact on the quality of your results and the quality of your work day. Test Driven Develoment (TDD) is one of them. If you are a software developer, you want to buy, read and study this book.
    TDD fits development into a three micro-phase cycle: create a test that embodies your requirement, write code that passes the test, make the code run clean. Each phase has different goals, patterns and pitfalls. Like any good coach, Beck walks you through these in detail. He uses multiple examples: most notably a business model in Java and a unit testing framework in Phython. He follows up with a question and answer section that reviews common patterns in test driven development cycle.
    The level of learning involved in doing TDD is profound. The best way to read the book is to do the book. Skills come from doing not reading. I did the examples (in another language) and it made all the difference in what I learned.
    A footnote for managers: TDD is the opening wedge for a set of practices known as extreme programming (XP) or agile development. Test driven development is powerful enough to work on its own for the single delevoper. If you want to realize its full value, however, you need to embrace the full set of XP practices for the whole organization.
    47 internautes sur 52 ont trouvé ce commentaire utile 
    Good introduction, but light on real-world development 28 novembre 2003
    Par Amazon Customer - Publié sur Amazon.com
    Format: Broché
    If you've never done or are curious about TDD, this is a great book to carefully walk you through learning how and why to do it. After following its practices a bit, I've also found it an indispensible way to write new projects, modules, and code. However, the book doesn't address what happens when:
    - The code base is old, and doesn't have any tests or isn't designed testable. It makes it hard to do anything other than introduce integration-level tests and tweak to success.
    - You're writing UI code for a serious application. It's straightforward to solve for a dialog framework, but when you're integrating with a major windowing framework that embeds serious functionality (Avalon, in my case), there are a whole set of issues he doesn't talk about.
    - Design is part of your deliverable. I don't disagree that you can get pretty reasonble designs out of TDD & refactor. But I *do* disagree that, in practice, you get designs intended to version well, that your company is willing to support for the next decade or more. I've seen the code produced, and it just doesn't happen.
    A good introduction, nonetheless. But watch out before you put on the preacher-hat after reading it and doing the exercises -- at least try to do it in part of one large, real-world product.
    50 internautes sur 57 ont trouvé ce commentaire utile 
    A decent introduciton 12 mars 2004
    Par Jason - Publié sur Amazon.com
    Format: Broché
    This Kent Beck title is an introduction to the world of Test-Driven Development (TDD). The book teaches the concepts of TDD by working through two complete sample projects. Along the way, Beck gives the reader valuable insight into the thought process and techniques behind successful test-driven development. When the reader has finished working through these sample projects, he should know enough about TDD to get started working on a TDD project.
    The book is divided into three sections. The first two sections are each walkthroughs of the aforementioned sample projects using TDD. The third section is a collection of notes and useful tips to try to get the most out of TDD. If you've ever read anything from Beck, then you should be familiar with his style. If you haven't, Beck is an engaging enough writer, and the text flows smoothly and is fairly pleasant to read.
    It would help to be familiar with some member of the xUnit family prior to reading this book. Beck uses Java and JUnit for the first section, but never really goes into discussing the JUnit API. Readers unfamiliar with xUnit may have no idea how to proceed with writing their own tests using one of these frameworks. True the API is simple enough that its functions may be ascertained simply by reading the code, but this is no reason not to provide explanation. The second sample project is an actual implementation of xUnit, so a bit more information may be gleaned here. Beck made the curious decision to use Python as the language of implementation for the second project, although he does provide explanation of the language's fundamentals. Finally, none of the sample projects are really complicated enough to do more than get us going on the path of TDD. There will still be many hurdles to climb when working on a real-world project.
    If you are seeking a basic introduction to test-driven development, then you might enjoy this title. If you are a Java developer interested in exploring TDD more in-depth, there are better books out there.
    12 internautes sur 13 ont trouvé ce commentaire utile 
    Intentionally slow-paced; this is a book on fundamentals 28 mars 2006
    Par Luke Meyers - Publié sur Amazon.com
    Format: Broché
    Many other reviewers have, with some justification, bemoaned the crunchingly slow pace of this book. Yes, the book moves through its examples slowly. Yes, sometimes Beck's mock humility comes off more than a little snide. It's not perfect on those counts, but please keep in mind that this is a book about a _process_, not a _result_.

    The first example takes up almost half the book just to go through a pretty minimal implementation of a multi-currency representation for money. If this were a book about how to implement money representations, it would be a dismal failure. But of course, that's not the point at all -- the point is to use an example that's simple (so as not to be distracting), but just complex enough to produce adequate talking points to drive a discussion about test-driven development (TDD).

    TDD is incredibly important, surprisingly late in arriving as a TLA unto itself, and Beck certainly gets points (cf. the review about "90% is just showing up") for producing a good straightforward introduction that's sorely needed. Nobody's going to come away from this book feeling filled to the brim with facts and sophisticated techniques. It's a short book (around 200 pages), and its pace is unhurried. What it does is focus on _fundamentals_.

    TDD is all about buyin -- once you "get religion" and become "test-infected" (per Gamma), you've got a solid basis to grow from. It's about habits, and habits can be hard to teach. What's obvious to one person is mysterious to the next. Beck's approach of "sit here with me and listen to my thoughts on a simple, representative problem" is perfectly adequate. It concedes (repeatedly) that some of the steps are obvious, but the pages quickly and one never feels truly bogged down. He's really just teaching a handful of concepts throughout the whole book. You could write the concepts in a single paragraph; that's how much real, critical information is here. But it's _really good information_, and sometimes the key to grasping a fundamentally new (to you) viewpoint or idea is just hearing it rephrased for the 101st time, this time in words your brain is prepared to listen to.

    So... it's a quick read, maybe a little pricey on that count. I'd say buy it anyway, and recoup the investment by loaning it to others on your team.

    TDD is an incredibly beneficial infection; it's worth exposing yourself to a plainspoken explanation like this. You'll probably know within 50 pages whether you agree.
    23 internautes sur 28 ont trouvé ce commentaire utile 
    From a Software Tester's Perspective 6 avril 2004
    Par Randy Rice - Publié sur Amazon.com
    Format: Broché
    I enjoyed reading this book, however I must advise that non-coders will probably have difficulty in staying with it. I don't mean that as a put-down of any kind. It's obvious that the intended audience is the developer who is trying to understand the concept of test-driven development. A tester, however, would learn in this book that test-driven development uses tests that are different in nature and rigor than those commonly thought of as "unit tests."
    I think Beck does a good job in explaining test-driven development in a way that is easy to understand. I still have some concerns about the nature of test-driven development, such as the emphasis on function over design. But I think Beck achieved a reasonable goal of presenting by example what test-driven development is all about.
    The goal of test-driven development is a reasonable way to achieve "clean code that works - now." As a tester, I think the awareness of test-driven development is a good thing. I also think that this technique must be combined with other methods, such as getting quality requirements, verification and validation, to achieve a final result that meets the users' needs.
    Readability - 4
    Coverage of topics - 5
    Depth of coverage - 5
    Credibility - 5
    Accuracy - 5
    Relevance to software quality - 5
    Overall - 5
    Ces commentaires ont-ils été utiles ? Dites-le-nous


    Commentaires

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