Use Case: Handle multiple Features in one test codeunit

[lvanvugt]

This issue is to get clearance (and eventually implement) on how TestScriptor should handle test codeunits with multiple FEATURES.

Current Situation

When creating a new FEATURE this leads to a new test codeunit that complies with the implicit principle that one codeunit contains only one FEATURE. The FEATURE tag will (only) be stored in the OnRun trigger.
But existing test codeunits can contain multiple features (with each SCENARIO, i.e. test function, having the applicable FEATURE tag placed within the realm of the test function).
TestScriptor page does list them nicely, but creating new scenarios in such a codeunit does not work right.

Issues:

• selecting last scenario in test codeunit in TestScriptor and creating new one will create indeed a new SCENARIO/test function, but only store FEATURE tag in OnRun, making the SCENARIO an orphan (as it is not clear to what FEATURE it belongs
• selecting a non-last scenario and creating a new one will indeed create a SCENARIO entry in TestScriptor, but no test function

Wanted situation

1. A function that can split up existing test codeunit with multiple FEATUREs into multiple test codeunits with each of the holding only one FEATURE (with its related SCEANRIOs)
2. Allow test codeunits to (keep) contain(ing) multiple FEATURES and
   • place with each test function (SCENARIO) the FEATURE it belongs to
   • add new scenario with FEATURE based the existing scenario selected in the TestScriptor