Another possible solution occurred to me:
put your scenarios twice into the story file and select the dev and prod
environment by meta filter:
Scenario: my test (prod)
Meta: @env prod
...
Examples:
|action|num|response|
|about|55|200|
|home|46|401|
Scenario: my test (dev)
Meta: @env dev
...
Examples:
|action|num|response|
|about|60|200|
|home|93|401|
this way meta filter "+env prod" will match the production scenario and
"-env prod" or "+env dev" matches the other scenario.
You still have to implement some way to pass the environment via a
property or evaluate a shell environment variable.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
