Class-based scenarios as alternative to existent method-based implementation
Since current scenario implementation transforms method to class at runtime, it is reasonable to have class-based scenario implementation which will be much simpler to use behind the scenes.
This class should be based on Scenario and do not break compatibility.
The only required method is run() which is actually a body of scenario.
Blueprint information
- Status:
- Started
- Approver:
- Boris Pavlovic
- Priority:
- Undefined
- Drafter:
- Alexander Maretskiy
- Direction:
- Needs approval
- Assignee:
- Staroverov Anton
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
- None
- Started by
- Alexander Maretskiy
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
[Spec] Introduce class-based scenario implementation
https:/
https:/
Gerrit topic: https:/
Addressed by: https:/
Moving set of scenarios into separate classes
Gerrit topic: https:/
Addressed by: https:/
Moving of Neutrone scenarios into separate classes
Gerrit topic: https:/
Addressed by: https:/
Port all Sahara scenarios to new style
Gerrit topic: https:/
Addressed by: https:/
Update of docstrings to support common-style scenarios
Gerrit topic: https:/
Addressed by: https:/
Moving of Volumes scenarios into separate classes
