CODEWITHSUNDEEP
c#unit-testingmstest
Lukáš Lánský
Lukáš Lánský

Reputation: 4932

DataTestMethod vs TestMethod

I started to use MSTest 2 DataRow attributes to check multiple cases in a single test:

[TestMethod]
[DataRow(1, 1, 2)]
[DataRow(1, 2, 3)]
public void AdditionWorks(int op1, int op2, int expectedResult)
{
    Assert.AreEqual(expectedResult, new Sut().Add(op1, op2));
}

It works nicely, both in NCrunch and in CI. Only now I noticed that there is special attribute DataTestMethod that is supposed to mark such tests instead of TestMethod.

Is there a difference? A reason to use one variant in particular?

Upvotes: 32

Views: 11682

Answers (2)

Nkosi
Nkosi

Reputation: 246998

Both attributes work because the same attributes are defined in the same namespace as the previous version of MSTest. This was done for backward compatibility.

Reference :

Taking the MSTest Framework forward with “MSTest V2”

Github: Unit Test Samples

Upvotes: 17

Nathan
Nathan

Reputation: 889

ShreyasRmsft commented the following on GitHub:

Hi @cactuaroid DataTestMethod is not needed. Go ahead and use TestMethod with DataRows to data drive your tests. For any more doubts follow the official docs at https://github.com/microsoft/testfx-docs

https://github.com/microsoft/testfx/issues/614

https://github.com/microsoft/testfx-docs/issues/64

So, according to Microsoft, it is preferred to use TestMethod over DataTestMethod.

Upvotes: 19

Related Questions