Is your feature request related to a problem? Please describe.
There should be a way to define a custom scenario, just as it is possible to define a custom user.
Describe the solution you'd like
A step implementation that specifies which scenario to use, which accepts input via context.text.
The input is scenario specific.
If no namespace is specified, it is assumed that it's a scenario class in grizzly.scenarios.
If this step is not present, it is assumed that it works as it is now, e.g. the scenario is IteratorScenario and the step `And repeat for ".." iterations" is used to control it.
The scenario class type should be saved in GrizzlyContextScenario and current (user) class_type property should be renamed to user_class_type.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
There should be a way to define a custom scenario, just as it is possible to define a custom user.
Describe the solution you'd like
A step implementation that specifies which scenario to use, which accepts input via
context.text.The input is scenario specific.
If no namespace is specified, it is assumed that it's a scenario class in
grizzly.scenarios.If this step is not present, it is assumed that it works as it is now, e.g. the scenario is
IteratorScenarioand the step `And repeat for ".." iterations" is used to control it.The scenario class type should be saved in
GrizzlyContextScenarioand current (user)class_typeproperty should be renamed touser_class_type.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.