Backwards Compatibility: TestMethods require zero parameters

Description

Upon upgrading unit tests from legacy MSTest to MSTest v2, I ran into the following breaking change. TestMethods throw exceptions if there are parameters, rather than getting skipped.

Steps to reproduce

Repro code:

    [TestClass]
    public class UnitTests
    {
        [TestMethod]
        public void Works()
        {
            Assert.IsTrue(true);
        }

        [TestMethod]
        public void Breaks(string name)
        {
            Assert.IsTrue(true);
        }

        [TestMethod]
        public void AlsoBreaks(bool flag = false)
        {
            Assert.IsTrue(true);
        }
    }

Expected behavior

Legacy MSTest would ignore these methods completely. No errors or exceptions and they wouldn’t get run. It would be somewhat useful if “AlsoBreaks” would get run using the default parameter values.

Actual behavior

Unit test framework throws a cryptic exception: “Parameter count mismatch”.

Environment

Version .18 of MSTest on VS2015

[pvlakshm]

How about this as the error message: Only data driven test methods can have parameters. Did you intend to use [DataRow] or [DynamicData]?

[jayaranigarg]

@MikeChristensen :

        [TestMethod]
        public void Breaks(string name)
        {
            Assert.IsTrue(true);
        }

We believe the only scenario user would write such a test where test method takes parameters would be when he wants to pass some data to the test and want to run as a data-driven test. But since no data is provided by the user, the only possible explanation to that would be that the user actually forgot to specify the data due to some reason. So rather than skipping the discovery(behavior of MSTestv1) where User may think tests are running successfully, it would be better if we flash a error message informing him that he missed specifying parameters(behavior of MSTestV2). Keeping the current behavior of MSTestV2 as it is makes more sense to us. Please share your thoughts in this?