This can be convenient when splitting various scenarios into separate feature files. In practice, need to split scenarios between different files comes when they have different backgrounds. Since there can only be one background per feature file, split will be necessary.
After splitting, same feature class cannot handle both feature files. If the feature class could support multiple feature file attributes, then this limitation would be removed.
e.g. currently in the test solution there are 2 feature classes: AddTwoNumbers, and AddNumbersTo5. These 2 feature classes could be consolidated into 1 if the above limitation is resolved.
This can be convenient when splitting various scenarios into separate feature files. In practice, need to split scenarios between different files comes when they have different backgrounds. Since there can only be one background per feature file, split will be necessary. After splitting, same feature class cannot handle both feature files. If the feature class could support multiple feature file attributes, then this limitation would be removed.
e.g. currently in the test solution there are 2 feature classes:
AddTwoNumbers
, andAddNumbersTo5
. These 2 feature classes could be consolidated into 1 if the above limitation is resolved.