i wondering whether there're tools assisting users in writing stories jbehave ?
please don't "write stories jbehave".
have conversations business, , capture scenarios talk about, in close language can. write down , use jbehave map natural language steps.
this jbehave's aliases for; can capture conversations rather forcing them form have.
if try make conversations match existing framework, you're programming using different kind of language, , of problems bdd designed still there. you'll translating "jbehave steps" business language instead of code. worse, because it's english, people think understand you're doing, instead of recognizing might have got wrong. if you're using jbehave way, might use a dsl, @ least doesn't provide illusion.
if find there's ambiguity in business saying , want constrain language use, talk rather doing in jbehave. may want read sections on "ubiquitous language" , "core domain" in eric evans' book, "domain driven design", make conversations have more effective.
conversation, not automation, heart of bdd.
Comments
Post a Comment