commit 19e2db3503e76bd3cd70a727f64c9cfd7396a1bb
Author: Mauro Talevi
AuthorDate: Wed Sep 12 08:48:46 2012 +0100
Commit: Mauro Talevi
CommitDate: Wed Sep 12 08:48:46 2012 +0100
Added article
diff --git a/site-frontend/src/site/content/users-experiences.html
b/site-frontend/src/site/
You could use table transformers:
http://jbehave.org/reference/stable/tabular-parameters.html
Examples:
{transformer=env}
|action|num|response|
|about|55|200|
|home|46|401|
where "env" is registered as a custom transformer that reads an env
variable and correspondigly adapts the table content.
Mauro Tal
Mauro Tal
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
...
E
