SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Bootleg TDD

suzuki avatar
suzuki
12 diapositives · 416 Views · Sep 15, 2014

Bay Area ColdFusion Users Group November 19, 2008. Bootleg TDD. Outline. Who are we? Testing Fundamentals The TDD Controversy The Cloak of Testability What you've been waiting for Back at Work. We are guys from MXUnit.org. Unit Test Framework && Eclipse Plugin for ColdFusion

Bootleg TDD - slide 1
01 / 12Bootleg TDD
1 / 17

Télécharger la présentation

Bootleg TDD
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Bay Area ColdFusion Users Group November 19, 2008 Bootleg TDD

  2. Outline • Who are we? • Testing Fundamentals • The TDD Controversy • The Cloak of Testability • What you've been waiting for • Back at Work

  3. We are guys from MXUnit.org • Unit Test Framework && Eclipse Plugin for ColdFusion • Bill Shelton and Marc Esher • CF and Java developers who test all the time and started MXUnit to support our needs • We also want it to work for you, that's why we're here!

  4. Testing Fundamentals • Why do we test in the first place? • Seems like an obvious question, but think about it. • What do we test? • When you test, what are you looking for? • Examine discrete aspects of system (db, cfc/service, UI, integration, end-to-end)‏ • When do we test? • Do you test before, during, or after you write production code?

  5. The TDD Controversy • ”Uncle” Bob Martin (ObjectMentor)‏ • ”...my thesis is that it has become infeasible ... for a software developer to consider himself professional if he does not practice test driven development.” • ”...a test driven developer does not write a line of production code until he has written a failing unit test, and no production code can be written until there is a failing unit test.” http://www.infoq.com/interviews/coplien-martin-tdd

  6. The TDD Controversy (cont.)‏ • Cedric Beust (TestNG)‏ • ”Don't you feel a bit dirty? What with all those books ... telling you you should be doing TDD, and otherwise you are not professional?Is it just me? I try to do it... sometimes it feels right, sometimes it doesn't..."Need citation! • ”I especially dislike the efforts of TDD extremists who are trying to make developers feel bad whenever they don't use TDD, or lead them to think that something is wrong with the way they write their software. ”

  7. Who's Right?

  8. What Bill and Marc Say • Just write your tests and make sure code is testable. • Bootleg TDD - Test Focused Development (TFD) : Write tests as much as possible and whenever it makes sense. • Testability naturally leads to clean code and a clear design • Agility – Testable code is also agile, allowing for quicker changes

  9. What you've been waiting for • What does untestable code look like? • What does testable code look like? • And MXUnit, of course ...

  10. Back at Work • When you get back to work ... • Download and install MXUnit and go through docs • Get involved! http://groups.google.com/group/mxunit • Testing is as just hard as writing code, but your code will be better if well-tested Your code is only as good as the tests that execute it.

  11. Test and be happy

  12. References • InfoQ : Coplien and Martin Debate • http://www.infoq.com/interviews/coplien-martin-tdd • InfoQ: Design for Testability (Cedric Beust)‏ • http://www.infoq.com/interviews/beust-designing-testability • The Flawed Theory Behind Unit Testing (Michael Feathers)‏ • http://michaelfeathers.typepad.com/michael_feathers_blog/2008/06/the-flawed-theo.html