Use Case: Handle multiple Features in one test codeunit #84
Labels
enhancement
New feature or request
version B
Next to be picked up (but needs probably some detailing)
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:
Wanted situation
The text was updated successfully, but these errors were encountered: