In preparation for the upcoming series of job interviews that I will no doubt have, I am trying to stay well disciplined in reminding myself about some gotchas in core Java that tend to come up as "technical tests".
I've just taken a look into Behaviour Driven Design and I can see why an old colleague has been name-dropping about it lately. My initial take on it it that it is still test-driven development, but the subtle change in naming conventions helps the developer to stay focussed on what the customer has specified. Keeping the business language in the code, allowing the tests to read more like specifications. Saying something "should" behave in a particular way instead of stating what you are testing.
Hopefully I will have a chance to try out JBehave soon.
Post a Comment