Mortgage Driven Testing

Derived from this post back in January 2013, and subsequent discussions, Mortgage Driven Testing is one of those terms that gets bandied about in the testing community on occasion. Matt Wynne also spoke on a similar topic at SkillsMatter. However, I think Matt’s interpretation can be applied more broadly, so here’s my view of what the Mortgage Driven Testing (MDT henceforth) charter might look like:

We have discovered that there is money to be made from this testing lark with rich veins of ignorance to be mined in both fearful testers and under-informed project managers/teams. We who subscribe to the MDT approach have therefore come to value:

[1] fragile GUI level test automation over robust, service and API layer focused checks

[2] lengthy and difficult to maintain manual test scripts over intelligent and reactive exploratory testing

[3] rigidly enforced processes over continuous learning and improvement

[4] a distinction between specialist roles over cross-functional teams

[5] certification over reputation

[6] metrics over meaning

That is, we value the items on the left over the items on the right because the items on the right are scary, require additional effort and potentially threaten our livelihood.

The list above is a draft. I expect to refine it further, but if you have any suggestions or modifications, I’d love to hear about them.

Thanks to Paul Berry and Richard Bradshaw for inspiring the post.

- Simon

2 thoughts on “Mortgage Driven Testing

  1. It is possible to mount a perfectly reasonable defence for this method of working (not that I’m personally defending it) and, again, this parallels the developer shoring up the (perceived) sides of their position in their organisation.

Leave a Reply

Your email address will not be published. Required fields are marked *

GiottoPress by Enrique Chavez