Test Driven Development (TDD) we write a test case first, application code afterwards and then we test the application code based on the test cases written earlier.
Any novice programmer can be confounded by this paradigm that TDD offers wondering how do you write a test case for an entity that does not exist. So Dan North came up with a solution suggesting that instead of writing test one should think of specifying behaviour. So that gave birth to Behaviour Driven Development.
Now BDD is make more sense to a novice programmer like me than TDD. Therefore in the light of this i want to know Marco is, that how can i use BDD to specify the so called "behaviour" when the OOP principles are already there. OOP model says that "function or method" is a behaviour which makes sense. So it follows logically that behaviour is an action, that again makes sesnse to me.
This is what i would like to know, how can BDD help me to model the intention of the user?
Being a student of natural language processing and data mining i can see the worth of BDD and its exponential growth in future too but i must connect the dots together. I believe behaviour and intention are different, from the perspective of a user.
But what confounds me now is, how will i model and test the "intention" of the user in the light of BDD approach with Javascript?