Dissociate tags and extra_options settings
Categories
(Testing :: Raptor, task, P3)
Tracking
(Not tracked)
People
(Reporter: sparky, Unassigned)
Details
We currently have the tags and extra_options being treated in the same way, i.e. anything in tags is in extra_options.
This bug is for dissociating these two settings and have them be treated differently. We have the current behaviour because we decided to start with moving everything to tags. I think we're at a point now where we can start moving settings from extra_options and adding them to tags.
This will let us start using the fields properly where extra_options changes trigger the creation of new data series while change to tags do not.
I propose we use the following definition for where options should be placed:
Tags: Options which describe the test but do not affect/modify the test.
Extra-options: Options which change how the test runs (e.g. conditioned profiles)
Updated•3 years ago
|
Description
•