Sunday, April 15, 2012

Rethinking Automated Testing

While you’ve been worrying about your BDD adverbs the iFart dev just made $40,000.

Can you give 140 char synopsis of "opportunity cost of TDD?"

Is always a "Best Practice"? Is there even any such thing? When shouldn't you use it? What could you do instead?

Testing implementation is terrible terrible terrible.

The pendulum is swinging back and forth in the TDD and developer-testing world...
I blogged over two years ago about Testing Backlash and then again one year ago Are you too agile for TDD/BDD?

PendIt seems the time has come for the pendulum to swing by once again. In an almost mystical conjunction a lot of alpha geeks are voicing current "new" insights about automated testing and TDD.

Maybe this is the developer community climbing the ladder to another stage of competence or to another stage of grief (the viewpoint is probably depending of the pains in your current project)… but maybe it is just that alpha-geeks like any other intelligent beings are getting bored after a while and turn to new topics.

Anyways, here is a list of the recent tide of "let's rethink automated testing":

Just for completion I am reenumerating older reflections on the topic:

Tudor shows in When testing does not cut it that testing is not always the best alternative to ensure certain properties of a software system.

1 comment:

Related Posts Plugin for WordPress, Blogger...