Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

Tests are grouped under the "No Traits" section in the Test Explorer even though the class has a [Trait] attribute #684

Open
blackdwarf opened this issue Jul 23, 2016 · 5 comments

Comments

@blackdwarf
Copy link

Cross-post from dotnet/core#134

Cross posting from xunit/xunit#889

I have set up my controller tests for a .net core web api xproj.

I have a TraitAttribute on the class, but it's not showing up in the Test Explorer in VS.

My dependencies have "dotnet-test-xunit": "1.0.0-" and "xunit": "2.2.0-" and the test runner is set up as "testRunner": "xunit".

Have I hit a bug or am I doing something wrong? I'm hoping I'm doing something wrong 😄

/cc @TheBeardedLlama

@mlorbetske
Copy link

@blackdwarf iirc this is something that's not accommodated by the protocol used by dotnet-test at the moment. @piotrpMSFT is that right?

@TheRealPiotrP
Copy link

@livarcocc though a design for traits has been discussed, I don't believe it has been implemented. Is that correct?

@MedAnd
Copy link

MedAnd commented Aug 8, 2016

@piotrpMSFT Also experiencing this issue... seems MSTest V2 Framework for .Net Core supports the ability to place the TestCategory attribute at the level of a class or assembly. Wonder why other unit test frameworks cannot do the same?

Moreover test discovery is failing for xUnit in VS2015 when target is x64 as per this issue: xunit/xunit#850 (comment)

@zwcloud
Copy link

zwcloud commented Nov 15, 2016

When will this be implemented? Or can I implement that myself? @piotrpMSFT
Is dotnet-test-xunit open sourced somewhere?

@olivif
Copy link

olivif commented Jan 7, 2017

any news on this? @piotrpMSFT

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants