Added constants for hierarchical naming

[Haplois]

• Added constants for hierarchical naming.
• Reduced dependency surface of the AdapterUtilities package.

[Haplois]

We're adding a TestProperty to store multiple levels of a name. I am calling it HierarchicalName. Any recommendations about the naming?

HierarchicalName property is an array, which holds these for a TestCase:

• Namespace
• Class
• TestGroup
• DisplayName
• Theory / DataRow

[peterwald]

HierarchicalName property is an array, which holds these for a TestCase:

• Namespace
• Class
• TestGroup
• DisplayName
• Theory / DataRow

I'm ok with the name HierarchicalName or HierarchyName. We shouldn't need an entry for Theory/DataRow. That is captured by TestGroup & DisplayName.

In the case of a "Fact" test, you would have a Namespace/Class/(blank)/DisplayName and in the case of a "Theory" test you would have a Namespace/Class/TestGroup/DisplayName where TestGroup captures the "test method" level and DisplayName would be different for each data driven test case. The way we handle this today in the test hierarchy is if there is only one DisplayName in a TestGroup, then the TestGroup level is removed.

[peterwald]

What about using just the name Hierarchy for the property.

[Haplois]

What about using just the name Hierarchy for the property.

Sounds better.

[peterwald]

Looks good with a few minor changes.

[AbhitejJohn]

Could the HierarchyName property be a dictionary instead, so both setting/retrieving is easier to understand and uniqueness of values is guaranteed? We could serialize/deserialise this the way we want internally,

[Haplois]

Do you mean like a <string, string> directory with set keys on the adapter?

[AbhitejJohn]

Gosh, I dont have a good way of responding to notifications from github. Yes, I meant a <string,string> property bag.
/cc : @Haplois