Well I think that the scenario matcher should match wiki page names so this could be easily done using existing code. The configuration part is a bit tricky as, it is passed by the constructor and I don't see any getter/setter. Mybe this should be exposed, so I could override the configuration for the reporter of the scenario, so that you could run the scenarios in Maven and get an xml report and run the scenario in eclipse and get a plain text report. Emmanuel
On Wed, Jan 14, 2009 at 12:11 AM, Mauro Talevi <[email protected]>wrote: > Emmanuel Hugonnet wrote: > >> Hi, >> My second problem is that the Configuration is injected in the Scenario >> constructor, but there is no configuration using the maven plugin so I can't >> specify the reporter from outside my scenario, or I should have a >> MavenJunitScenario that can define the reporter in the configuration. >> Is there another way ? >> I think that having JBehave taking scenarios from an existing wiki tool >> and reporting in a xml format (with integration to maven) would be great. >> Our business analysts would have an editor, we could have graphical >> reports in the continuous integration server to display our advancement. If >> we could have an id for each story we could even have some history attached >> to it: like when it was fully implemented, when it broke etc. >> >> > > It's certainly an interesting idea and my feeling it shouldn't be difficult > to achieve. > > Could you us more details of how you plan to use JBehave with the wiki so > we can help you and possible implement any additional feature required? > > Thanks > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
