Improved scenario organization (backwards compatible parrot-friendly enhancement)

[PageTMcEneaney]

Issue

A single list is sufficient when we have limited scenarios, but we're finding we have too many scenarios and it can be difficult to find the one you need. We have multiple locales, audiences, products & api responses that we need to mock, which results in a long list with redundant keywords in the title

Examples

Here is an example of the default view of scenarios vs how long a hidden list can be

Proposed Solutions

I would like to start a discussion around this topic to find the easiest way to add some additional organization. Here are some Ideas I had (including very quick sketchy mock ups just to illustrate the idea)

1. Folders or Drawers - Each describe in the parrot-friendly syntax would act as a folder or layer of organization, and each it would act as the scenario. For the example above you could have something like Locale > Single / Multi > Scenario

2. Tags or Labels - Each it could accept an optional array of 'tags' to be applied to the scenario.

[smackfu]

Just thinking out loud but option (1) would be fairly straightforward to do in a backwards compatible way:

• Have nested describe blocks create a scenario with those names appended with some "magic delimiter" string. e.g. "Full Success >>> has one friendly ship"
• An updated extension would know how to interpret ">>>" but a non-updated one would still work and just show a single list.