[jbehave-dev] [jira] Closed: (JBEHAVE-123) JBehave configuration classes

2008-07-25 Thread Elizabeth Keogh (JIRA)

 [ 
http://jira.codehaus.org/browse/JBEHAVE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Elizabeth Keogh closed JBEHAVE-123.
---

Resolution: Fixed

Andy Palmer and I paired on this; introduced the Technique class.

 JBehave configuration classes
 -

 Key: JBEHAVE-123
 URL: http://jira.codehaus.org/browse/JBEHAVE-123
 Project: JBehave
  Issue Type: New Feature
Reporter: Elizabeth Keogh
Assignee: Elizabeth Keogh
 Fix For: 2.0


 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!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[jbehave-dev] [jira] Created: (JBEHAVE-124) Eclipse can't find the test to run when it's in JBehave's jar

2008-07-25 Thread Elizabeth Keogh (JIRA)
Eclipse can't find the test to run when it's in JBehave's jar
-

 Key: JBEHAVE-124
 URL: http://jira.codehaus.org/browse/JBEHAVE-124
 Project: JBehave
  Issue Type: Improvement
Reporter: Elizabeth Keogh
 Fix For: 2.0


This works fine when we have the source available. Is there a way of including 
the source for Scenario in the jar, to get Eclipse to notice that there really 
is a test?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




[jbehave-dev] [jira] Created: (JBEHAVE-126) GivenScenarios

2008-07-25 Thread Elizabeth Keogh (JIRA)
GivenScenarios
--

 Key: JBEHAVE-126
 URL: http://jira.codehaus.org/browse/JBEHAVE-126
 Project: JBehave
  Issue Type: New Feature
Reporter: Elizabeth Keogh


As someone writing scenarios, I want to be able to use another scenario as a 
Given, so that I don't have to write big long scenarios.

Not sure how this would work - at the moment we can get around it on the code 
side. I'm guessing we're looking for something like

Given the glider

where the_glider is a scenario file.

(What would we do if the_glider had two scenarios in it? Throw an exception, 
maybe?)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email