jbehaveuser edited a comment on Story JBEHAVE-785

Thanks. Going forward, I will post my queries in jbehave-user mail list.

I will explain the problem in simple context. My proposal is about isolating the parameter value from story file and keep the data's in table file. Presently using Jbehave, we can move a scenario data's to a .table file.
In the story file, there are lot many scenarios. For each scenario, we will have to create associated .table files.

If you take the above login example, there are 2 scenarios. one is valid login scenario with some input data's and another scenario is about checking invalid user with invalid input data's. In this case, I need to create 2 .table files to keep the data of these 2 scenario. I would like to keep these 2 parameters data in a .table file.

I would like to keep both of the above input data's in a single .table file(Login.table).

For example,

Login.table
------------
Scenarioname username password
----------- -------- --------
Login1 ABC correctpassword
Login2 XYZ invalidpassword

While executing a scenario, for example Login1 scenario, the Jbehave should able to pick the input param data from the respective row( Here the row is first one which is associated to Login1).

For each story file, I would like maintain a associated .table file.

Basically, I am looking some solution to avoid for creating .table file for each scenario in the story file.

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

Reply via email to