Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
I'm starting to find that there are multiple different things I might want to do, and the dependency injection mechanism isn't really working as well as I'd like for this.
It would be nice to produce a configuration that's easy to set up, and use that for everything. We could then have different ways of configuring JBehave, eg: environment-driven, settable, null (so you have to specify everything yourself), etc.
Going to have a play with this, driving it using the "broken scenarios only".
BTW, every time I get a "broken scenario" or "error output" story, I'm driving it by actually breaking a story. You won't see these broken stories checked into the build, but it's easy enough to replicate yourself!
Activity
Elizabeth Keogh
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Elizabeth Keogh [ sirenian ] |
Elizabeth Keogh
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
I would propose to:
- rename Technique -> ScenarioConfiguration (on the grounds that Technique is too vague a word)
- rename OurTechnique -> DefaultScenarioConfiguration
- move these two classes to scenario package.
Thoughts?
Mauro Talevi
added a comment - I would propose to:
rename Technique -> ScenarioConfiguration (on the grounds that Technique is too vague a word)
rename OurTechnique -> DefaultScenarioConfiguration
move these two classes to scenario package.
Thoughts? Mauro Talevi
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
I'd wait - the thing is slowly disappearing anyway as we move to a tell-don't-ask structure. The next step will be to pass the reporter into the runner, which will probably have to happen as we decide whether to break on pending or just truly broken steps, and change the output of the reporter accordingly.
So, hold up 
It served well as an interim measure for some very messy code.
Elizabeth Keogh
added a comment - I'd wait - the thing is slowly disappearing anyway as we move to a tell-don't-ask structure. The next step will be to pass the reporter into the runner, which will probably have to happen as we decide whether to break on pending or just truly broken steps, and change the output of the reporter accordingly.
So, hold up It served well as an interim measure for some very messy code. We now have PropertyBasedConfiguration, which allows us to do things like output all scenarios, fail the build on pending scenarios, etc.
Elizabeth Keogh
added a comment - We now have PropertyBasedConfiguration, which allows us to do things like output all scenarios, fail the build on pending scenarios, etc. Elizabeth Keogh
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
Andy Palmer and I paired on this; introduced the Technique class.