Description

MSTest has been through various strategies to generate test IDs and so far the changes have been done in a one choice only behavior. Through this ticket, we want to fix this issue by introducing strategies (via some enum) to let users decide how we should generate test IDs.

We have identified the following strategies:

• Legacy: strategy used by from v1 to v2.2.3
• Display name: strategy used between v2.2.4 and v2.2.10
• Data: new default strategy used from v3 forward

We have identified the following issues as impacted/fixed by this change:

• DataTestMethod skips DataRows that provide different data arrays, only keeping last #1016
• TestCase with DataRow attribute with null parameter ignored #1028
• DateTime equality test fails after upgrading from 2.2.3 #1121
• TestId no longer constant across test runs #1149

AB#1634557