Quality Assurance, BDD and Reusable Design.

Before we can talk about Quality Assurance we need to know exactly what we are talking about, the best definition so far is :

“A way of preventing mistakes and defects in manufactured products and avoiding problems when delivering products or services to customers”

Of course we all want that, we all want to deliver the best product we can and avoid mistakes while doing so. But the question is how to do that effectively.

BDD or Behavior Driven Development encourages collaboration between everyone involved in creating, and delivering a product to the customer. Developers, QA, Product Owners and various other stake holders (technical or non-technical) come together to create a product design that’s based on as you may have guessed customer behavior.

Sounds great but where does “reusable design” come into the picture ? And what is it ?

We have all heard (And developers reading this have used it) of reusable code. A piece of code that was written to do a certain thing, but that can be reused in other circumstances to do the same action but more often then not this is incidental or by accident. It should also be factored into design, this goes for user stories, bug reports, reporting of various things, code, tests, and anything that you have to do more then once.

BDD already inherently dictates this when talking about user stories, by looking at an example from wikipedia…