[
http://jira.codehaus.org/browse/JBEHAVE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261948#action_261948
]
Edward Staub commented on JBEHAVE-218:
--------------------------------------
The new page looks good - the key sentence, for me, is the last one on the page:
bq. _It constitutes a test harness that verifies the "production code" that is
found in the JBehave core modules._
FWIW, I suspect that most folks will assume, like I did, that the production
code under test was the game, trading system, etc. I could be wrong, though!
> Standardize and make file/directory layout configurable
> -------------------------------------------------------
>
> Key: JBEHAVE-218
> URL: http://jira.codehaus.org/browse/JBEHAVE-218
> Project: JBehave
> Issue Type: Improvement
> Components: Maven Plugin
> Reporter: Chris Jensen
>
> The maven plug-in for JBehave works all right, but it should default to
> standard maven archetype layout for test classes and the JBehave team should
> come up with a standard on where plain-text scenarios should live, what file
> extension they should have (to make them discoverable) and then allow that
> standard to be overridden.
> The documentation on the JBehave site should clearly present the standard
> layout and specify how it can be overridden.
> Reporting output should be included in the standard and should by default go
> where maven reports typically go, in a sub-directory of target.
--
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
