- Write a single spec. Script multiple runs. Use tags to define which scenarios to execute on each run
- Write a single spec. Script multiple runs. Use spec tables to define different assertions to perform on each run
- Write a spec. Duplicate a spec for each variation. Set up run in Using block of spec
- envrionment
- tenant
- language
- device?
- scenario with no tenant table
- scenario with tenant table
- current tenant
- current tenant is defined in scenario tenant table
- When a scenario does not have an @environment_ tag defined, it should be run against any/every environment
- When a scenario does not have a @tenant_ tag defined, it should be run againt any/every tentant
- When a scenario does not have a @language_ tag defined, it should be run against any/every language
- When a step does not have a 'target' table defined, it should be run against any/every target
- When a step has a 'targets' table defined, it should select the appropriate value from the targets definitions. if no definition exists for current context, it should use the 'all' target. if no 'all' target is defined, it should ??
- cuke_iterations
https://github.com/jmerrifield/cuke_iterations