Tooling: Add support for xUnit Traits in tests

[Eilon]

From https://github.com/aspnet/Testing/issues/136

We need a mechanism to pass through the data for xUnit's Traits and similar types of data from the test framework.

https://github.com/xunit/xunit/issues/487#issuecomment-127652743

[sayedihashimi]

TFS: 149249
Added it to the backlog, will get back here once we have more.

[herecydev]

Any update on this?

[shederman]

This has had quite a runaround, from https://github.com/xunit/xunit/issues/485, to https://github.com/aspnet/Testing/issues/136, and now here.

Is this where it's going to get fixed, or is the potato just going to get passed on?

Because it's really quite an annoying bug, have all these lovely traits for my tests, and they're just ignored.

[arashnorouzi]

I was wondering if there has been any updates on this.
Thanks.

[DerAlbertCom]

yep, currently i'm writing the the MSpec Test Adapter for DNX, and was searching for grouping the testing VS by traits. Because i would like to but the MSpec Subject there. After trying some hours i found this. So, please ;)

[sayedihashimi]

We are in the process of converting vs unit testing to be based on dotnet instead of dnx. Because of this we have not added any features to bs unit testing yet. After RC2 we should be able to add features like this.

[GunterGlad]

RC2 is out now and any update? Please?

[DaveSlinn]

Have Preview 2 of Tooling - still not working. Looking doubtful this will make it in for Tooling RTM.

[another-guy]

What is the status of this issue?

[dmccaffery]

@sayedihashimi this is killing me now that the only way to filter tests through dotnet test (msbuild) needs this info too!

[another-guy]

Any update? Is there any way to vote on this issue to make it a high priority???

As of v 14.0.25431.01 Update 3 VS seems to not treat the Traits... Running tests not based on traits is very annoying.

[webtools-bot]

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!