Allow all unit test types to be associated to a work item
The "choose a test" window that is displayed when associating an automated test to a work item only shows tests with an MS Test attribute. With VS now integrating other testing frameworks, like NUnit, it would be good if any test that shows up in Test Explorer (NUnit tests do) also show up in the Choose a Test window so they can be associated with a work item.
Can users who are interested in this uservoice item please reach out to me : atinb at Microsoft dot com?
I will like to understand the end goal in more detail and see how we can achieve it.
I'm using NUnit and was looking for the same. It's quite difficult to find information about that, why dont you put on TFS documentation that for the moment you only support MsTest? I created a StackOverflow question in case others have the same problem and just look for confirmation that with UT frameworks different from MsTEst, it cant be done.
Lisbeth Mogseth commented
I want what is described here: https://msdn.microsoft.com/en-us/library/dd380741.aspx with tests written in xUnit. As the original suggestion states, the xUnit tests are discovered by the Test Explorer (so it feels like part of the job is already done). The xUnit tests are run as part of our CI build steps and what I would like to do is to feed back results from those runs into Test Case work items so that I in the Test Manager (or web portal) can have a complete overview of the status (pass/fail) of manual system tests as well as automated unit tests and integration tests (not written in MsTest)
I also face the same challenge. We have written so many UTC using MSTEST and execution is difficult. MTM can solve this for us.
Gerhard Matzen commented
I think this is related to what I want. Specifically, I want the ability to associate native C++ Unit tests to Work Items of type Test Case so that I can import these test cases into Microsoft Test Manager (MTM) and run these tests from MTM. We already have a large number of C# unit tests and we have done a large amount of automation around MTM. We do not want to solve this automation problem again for native C++ Unit tests.