[
https://jira.codehaus.org/browse/JBEHAVE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285323#comment-285323
]
Mauro Talevi commented on JBEHAVE-655:
--------------------------------------
Comments are treated by JBehave as ignorable steps, but only if they appear in
a scenario. Anything before a Scenario keyword is not consider a step, and it
depends on the context. If nothing else is present, it'll end up being part of
the story description.
> a comment before "Scenario" ends up as package name in jbehave-plugin-jenkins
> -----------------------------------------------------------------------------
>
> Key: JBEHAVE-655
> URL: https://jira.codehaus.org/browse/JBEHAVE-655
> Project: JBehave
> Issue Type: Bug
> Components: Jenkins Support
> Affects Versions: 3.5.4
> Environment: jenkins 1.442, Jenkins xUnit plugin 1.32, JBehave
> Jenkins Plugin 3.5.4
> Reporter: Alexander Lehmann
> Priority: Minor
>
> When I run a story that has a comment as the first line of the text, the
> jbehave/xunit display in Jenkins takes the comment as test name and misses
> the story file name.
> {{!-- comment
> Scenario: User visits home page
> !-- a very simple test
> Given user is on Home page
> Then Home page is shown
> }}
> the resulting path is then (root)/!-- comment/User visits home page
--
This message is automatically generated by JIRA.
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
