Bringing discussion to the list:
Stefan Hübner (JIRA) wrote:
Oh, maybe I should have asked before altering the plugin to serve my personal
needs. I was assuming, that behaviours are - in a way - like unit tests. So I
put them into the src/test/java-folder instinctively. Now I know, my percept
Stefan Hübner wrote:
So this would boil down to placing behaviours/stories either in
"src/main/java" or "src/test/java" and scoping jbehave either in
compile or test scope.
The switch could be easily supported by a simple boolean configuration
option, I guess. The plugin then would create a cla
Stefan,
sorry for the long wait - getting back to jBehaving ...
Stefan Hübner wrote:
So this would boil down to placing behaviours/stories either in
"src/main/java" or "src/test/java" and scoping jbehave either in
compile or test scope.
The switch could be easily supported by a simple boolean
Hi,
Mauro wrote:
Bringing discussion to the list:
[SNIP]
I personally see behaviours as more along the lines of acceptance testing than
unit testing. So
rather than a replacement for JUnit, I would see it a replacement for Fit.
That said, some people might want to use BDD as a replacement
Hi Stefan.
Excuse me for wading in halfway through. I just want to add a couple of
observations or suggestions. Firstly, as I have been doing more and more
bdd-style projects, I have evolved into the following code structure:
- app [the application]
- src
- resources
...
- behaviour
Dan,
thank you for statements and sorry for the delay.
you wrote:
Hi Stefan.
Excuse me for wading in halfway through. I just want to add a couple of
observations or suggestions. Firstly, as I have been doing more and more
bdd-style projects, I have evolved into the following code structure:
Mauro,
for playing with the plugin I've compiled a tar ball comprising the
hellbound-examples like I use them.
The example contains three modules. "hellbound2-app" has got the
app-code as well as the behaviour classes (in the test-folder). The
second module "hellbound2-behaviours" contains just
