A Behavior Driven Development Intro By Dave Astels
So if it’s not about testing, what’s it about?
This article really boils it down and I as well as people Iâ€™ve talked to about testing, should read this.
When I was first told about testing from my good friend Dave Wanner, he described it so well. I didnâ€™t realize it, but I was â€˜writing testsâ€™ because I would create â€˜senarioâ€™sâ€™ with, ie. a console app , to try out a piece of code to make sure it did what it was suspose to do.
Later on, on others, it became strictly about â€˜code coverageâ€™ 80-90%, etcâ€¦ must have a test or you havenâ€™t done your job. Interesting.
Then in the larger corporation environment, the term â€˜testâ€™ was confused with what the QA folks were doing, it was confused with â€˜we canâ€™t test this without the databaseâ€™ , etcâ€¦ etcâ€¦ and of course everyone questioned how testing some â€˜unitâ€™ outside of the entire end to end wasnâ€™t a good â€˜testâ€™.
So, this article really is almost taking me back to the first introduction I had to testing. Maybe Iâ€™m wrong but it appears the language is changed in order to separate itself from the new definitions.
ie. TDD was fine, but it slowly means something else, so now we create term BDD which is, in many ways, the original TDD definition ?
But hey, decide for yourself :) Read it 🙂