[jbehave-dev] [jira] (JBEHAVE-785) Map the Scenario(from Story file) to data file(External file) in Jbehave

[jbehaveuser (JIRA)]

jbehaveuser commented on JBEHAVE-785 Map the Scenario(from Story file) to data file(External file) in Jbehave Thanks a lot. I hope the above idea looks like resolve the problem which i cited. To achieve the single table concept, I have added the Meta tag name in the below 2 scenarios and in a table. When the scenario begins executed, it should identify the respective row from the table based on mata tag name given in particular scenario. Scenario: Login1: User Logs into the Application with correct password Meta: @env Login1 Given I log into Application as valid user <username> with correct password <password> Examples: ../Login1.table Scenario: Login2: User Logs into the Application with incorrect password Meta: @env Login2 Given I log into Application as valid user <username> with invalid password <password> Examples: ../Login1.table Login1.table ------------ env username password Login1 ABC correctpassword Login2 XYZ invalidpassword When I tested with the above option, jbehave is not filtering the row based on meta tag, whereas it's executing a first scenario 2 times with both input rows and started getting some exceptions in the console. With the first input row, it's working fine and when it stared executing with 2nd row, I am facing this issue. Could you correct me, if I missed some other configuration in the above example?

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. 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