Update unit-testing-mstest-migration-from-v1-to-v3.md

Author: engyebrahim

docs/core/testing/unit-testing-mstest-migration-from-v1-to-v3.md

@@ -139,6 +139,19 @@ Choose the option that best suits your project setup. Both methods ensure your p
 
 If AreEqual, AreNotEqual, AreSame, or AreNotSame assertions cause errors, we recommend checking that the types being compared are compatible. If they are, consider adding explicit generic typing to resolve the issue.
 
+### DataRowAttribute Updates
+
+The DataRowAttribute constructors in MSTest v3 have been simplified to enforce type matching for parameters. This means you must specify values in DataRow that precisely match the types of the method parameters.
+
+**Example**:
+
+```csharp
+[TestMethod]
+[DataRow(1, "test")] // Correct: matches parameter types (int, string)
+public void MyTestMethod(int number, string text) { ... }
+```
+In cases where types don’t match exactly, MSTest v3 will now raise an error rather than attempting a conversion.
+
 ### Timeout Settings
 
 In MSTest v3, the handling of `Timeout` settings has been standardized to ensure consistent behavior across different .NET environments. This change may impact tests that rely on specific timeout values, especially if those tests are asynchronous or run under different frameworks.