Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dotnet core test support for the Visual Studio Test task #1566

Closed
matthew-horrocks opened this issue Apr 27, 2018 · 4 comments
Closed

dotnet core test support for the Visual Studio Test task #1566

matthew-horrocks opened this issue Apr 27, 2018 · 4 comments

Comments

@matthew-horrocks
Copy link

I've seen various comments, reports and suggestions that dotnet core test support for the Visual Studio Test task is on your backlog and will be addressed.

Is there a timeline for this work? Is it in progress? Is there a beta version of the task we can trial this with?

Thanks,
Matt

@mayankbansal018
Copy link
Contributor

@pvlakshm , I suppose we have a story planned for this, can you please share the plan here

@matthew-horrocks
Copy link
Author

I did wonder this morning if this would have been better asked at https://github.com/Microsoft/vsts-tasks/issues as it relates more to the VSTS Visual Studio Test task.

@smadala
Copy link
Contributor

smadala commented Jun 19, 2018

@PBoraMSFT Can you share plan for this?

@PBoraMSFT
Copy link
Member

@matthew-horrocks - this question is best suited for the vsts-tasks repo as it relates to the task, not the platform. However, I will answer it here since we have it going on.
dotnet core support in VSTest means different things for different people - it may mean one or more of the following:

  1. running dot net core tests using the assembly input
  2. Collecting code coverage using the 'Enable code coverage' - which is currently not supported (as code coverage doesn't support portable pdbs today, but can be worked around using full pdbs)
  3. Running tests by associating them with a test plan/test suite - which is currently not supported.

#1 works today with the the target framework specified in the console options.
We are currently working on #2 and expect it to become available in a couple of sprints.
#3 is in the works, but we have hit some roadblocks, so don't have an ETA to share at this time.

Hope this helps.

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

No branches or pull requests

5 participants