This feature adds an extra "Scenario" level in between use case and test case, to increase readability and sorting for users.
Now a scenario must be defined in the test case YAML file in order to use it within the platform. The first time a new scenario is mentioned it will be created automatically under the relevant use case. If the scenario already exists the test case will be added there.
Screenshots
Details
This change requires new tables and relationships, and is therefore not backwards compatible. While a manual migration may be possible, it is recommended to use a fresh seed for the database.
Background
This feature adds an extra "Scenario" level in between use case and test case, to increase readability and sorting for users. Now a scenario must be defined in the test case YAML file in order to use it within the platform. The first time a new scenario is mentioned it will be created automatically under the relevant use case. If the scenario already exists the test case will be added there.
Screenshots
Details
This change requires new tables and relationships, and is therefore not backwards compatible. While a manual migration may be possible, it is recommended to use a fresh seed for the database.
Checklist