So there has been this enormous discussion on the Yahoo TDD Group about testability: it was kicked off by��Marcus.�� I used this��dialogue as an opportunity to��explorer something my gut has been bothering me about. My gut has been trying to warn me that TDD, as I understand it, provides inadequate ...

MbUnit, my favorite xUnit Framework, is easy to extend.�� This tutorial will cover creating a new type of test fixture attribute��and test method attribute.�� There are basically two reasons for creating extensions: to solve a general need and solve a specific need.�� The need to create an extension for a��specific��context ...

MbUnit, my favorite xUnit Framework, is easy to extend.�� This tutorial will cover creating a new type of test fixture attribute��and test method attribute.�� There are basically two reasons for creating extensions: to solve a general need and solve a specific need.�� The need to create an extension for a��specific��context ...

It seems that I misunderstood Kelly Anderson and he wished to be included in the posting.�� Thanks again for straightening me out Kelly. :) Here is his reply: How do YAGNI and testability relate? If one subscribes to the point of view that the tests fulfill the roleof ...

It seems that I misunderstood Kelly Anderson and he wished to be included in the posting.�� Thanks again for straightening me out Kelly. :) Here is his reply: How do YAGNI and testability relate? If one subscribes to the point of view that the tests fulfill the roleof ...

From c2.com: Dependency Inversion Principle DIP: A. High level modules should not depend upon low level modules. Both should depend upon abstractions. B. Abstractions should not depend upon details. Details should depend upon abstractions. (http://www.objectmentor.com/publications/dip.pdf) Forces We wish to avoid designs which are: ...

From c2.com: Dependency Inversion Principle DIP: A. High level modules should not depend upon low level modules. Both should depend upon abstractions. B. Abstractions should not depend upon details. Details should depend upon abstractions. (http://www.objectmentor.com/publications/dip.pdf) Forces We wish to avoid designs which are: ...

And again I will start of with an exerpt from c2.com: Open Closed Principle OCP: Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification. (http://www.objectmentor.com/publications/ocp.pdf) BertrandMeyer first coined it in the first edition of ObjectOrientedSoftwareConstruction as follows: ...

And again I will start of with an exerpt from c2.com: Open Closed Principle OCP: Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification. (http://www.objectmentor.com/publications/ocp.pdf) BertrandMeyer first coined it in the first edition of ObjectOrientedSoftwareConstruction as follows: ...

I sent a questionnaire out to a bunch of people the other day.�� I thought that the community might find it interesting so here is what I can share. Here is the questionnaire, unaltered,��typos and all. The term testability in these questions is about the test subject.�� How ...

I sent a questionnaire out to a bunch of people the other day.�� I thought that the community might find it interesting so here is what I can share. Here is the questionnaire, unaltered,��typos and all. The term testability in these questions is about the test subject.�� How ...

Most of my reading lately has been for personal growth and focused on leadership and change.�� Not all of it is actually reading as I have a 2+ hour commute. Books Leading Change by John P. Kotter �� The 17 Indisputable ...

Most of my reading lately has been for personal growth and focused on leadership and change.�� Not all of it is actually reading as I have a 2+ hour commute. Books Leading Change by John P. Kotter �� The 17 Indisputable ...

Yet again here is an explanation for c2.com: YouArentGonnaNeedIt (often abbreviated YAGNI, or YagNi on this wiki) is an ExtremeProgramming practice which states: "Always implement things when you actually need them, never when you just foresee that you need them." Even if you're totally, totally, totally ...

Yet again here is an explanation for c2.com: YouArentGonnaNeedIt (often abbreviated YAGNI, or YagNi on this wiki) is an ExtremeProgramming practice which states: "Always implement things when you actually need them, never when you just foresee that you need them." Even if you're totally, totally, totally ...