Designing systems that work.
Contact us to get started today.

Test Deficit Disorder: A Silent Killer of Software

TDD is a serious problem. An outbreak of this uniquely degenerative disease can have a debilitating effect. In fact, it often proves deadly to software applications.
A development team infected with Test Deficit Disorder exhibits a marked aversion to testing their software. Often, they put off testing to the last possible moment, and then rush through it in a panic-induced state triggered by the disease.
To help you identify teams that are suffering from TDD, we’ve prepared a list of symptoms:
Buggy software
This is the most common indicator of the disease. Infected development teams always display this symptom.
Red eyes
Sufferers often experience feelings of frustration and hopelessness that lead to intense crying, especially near the end of development when bug counts skyrocket.
Sweaty palms
The disease goes to work on the nerves and gradually ratchets up stress levels.
Demophobia
A side effect of Test Deficit Disorder, demophobia is an overpowering fear of showing a client what you have so far.
If you’re afraid of being exposed to a development team infected with Test Deficit Disorder, don’t worry! There’s now a cure. As you might have guessed, it’s known as Test-driven Development.
Here at Architech, we’ve had our TDD shots and we get tested regularly (therefore we test regularly).
If you think your software might be at risk, give us a call and learn the facts about TDD. Don’t let Test Deficit Disorder compromise your systems.
To learn more about the cure, check out our white paper “Test-Driven Development: A Commitment to Quality”. Together, we can beat the disease.

TDD is a serious problem. An outbreak of this uniquely degenerative disease can have a debilitating effect. In fact, it often proves deadly to software applications.

A development team infected with Test Deficit Disorder exhibits a marked aversion to testing their software. Often, they put off testing to the last possible moment, and then rush through it in a panic-induced state triggered by the disease.

To help you identify teams that are suffering from TDD, we’ve prepared a list of symptoms:

  • Buggy software. This is the most common indicator of the disease. Infected development teams always display this symptom.
  • Red eyes. Sufferers often experience feelings of frustration and hopelessness that lead to intense crying, especially near the end of development when bug counts skyrocket.
  • Sweaty palms. The disease goes to work on the nerves and gradually ratchets up stress levels.
  • Demophobia. A side effect of Test Deficit Disorder, demophobia is an overpowering fear of showing a client what you have so far.

If you’re afraid of being exposed to a development team infected with Test Deficit Disorder, don’t worry! There’s now a cure. As you might have guessed, it’s known as Test-driven Development.

Here at Architech, we’ve had our TDD shots and we get tested regularly (therefore we test regularly).

If you think your software might be at risk, give us a call and learn the facts about TDD. Don’t let Test Deficit Disorder compromise your systems.

To learn more about the cure, check out our white paper “Test-Driven Development: A Commitment to Quality”. Together, we can beat the disease.

Leave a Reply