[
https://jira.codehaus.org/browse/JBEHAVE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maciej Madej updated JBEHAVE-745:
---------------------------------
Attachment: jbehave-named-bug.zip
Sample project with patched StoryRunner class, changed line is 365 (
addMetaParameters(scenarioParameters, storyAndScenarioMeta);)
> @Named annotation doesn't work in scenario when Examples table and MetaInfo
> is used
> -----------------------------------------------------------------------------------
>
> Key: JBEHAVE-745
> URL: https://jira.codehaus.org/browse/JBEHAVE-745
> Project: JBehave
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.5.4
> Environment: Windows XP, jdk6
> Reporter: Maciej Madej
> Attachments: jbehave-named-bug.zip
>
>
> Please take a look at below scenario.
> Meta:
> @supported_type A,B,C
> Given message with supported type
> When received with <field> field
> Then message is stored
> Examples:
> |field |
> |action|
> @Named annotation doesn't work when I want to inject @supported_type and also
> 'field' example value for this scenario.
> I guess problem is in StoryRunner class (lines 254-260). Memthod
> addMetaParameters is not called when scenario is parametrized.
> Can we invoke this method also for parametrized scenarios?
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
