Live-share: Allow guests to see the results of tests run via the Test Explorer in Visual Studio

Created on 12 Jan 2018  路  12Comments  路  Source: MicrosoftDocs/live-share

Note that developers starting the collaboration session (hosts) do not have this limitation. It is specific to participants joining a session.

The results of tests run via the Test Explorer in Visual Studio do not land in the common output window or errors list and therefore require access to the Test Explorer to see. We could enable sharing of these results with guests if there is sufficient interest.

testing feature-request on-roadmap pair programming vs

Most helpful comment

Any word on this? It is probably our biggest pain point currently with using Live Share with Visual Studio.

All 12 comments

I have a list of things from "first impression" while working with my boss several states away and this was one of the things we discovered in the first 5 minutes.

One thing I'd be curious about is Resharper test runner vs msbuild test-runner. We both use Resharper and until recently didn't even realize we needed the NUnit test runner package to run NUnit tests via msbuild.

I suggest adding the label "scenario: pair programming" to this one. For people who want to practice TDD or write other test types together, this seems essential.

@jawn Great suggestion! I just updated the tags 馃憤

Any word on this? It is probably our biggest pain point currently with using Live Share with Visual Studio.

Hi team. Is this feature available in Visual Studio 2017? I couldn't use it.

I now have the test runner available when I am a guest (after opting in to Insiders track). There is a weird bug though. Whilst I can always see the test list and the output, I can only run them once. After that, the Run buttons stay greyed out. The host can still run them however.

I now have the test runner available when I am a guest (after opting in to Insiders track). There is a weird bug though. Whilst I can always see the test list and the output, I can only run them once. After that, the Run buttons stay greyed out. The host can still run them however.

@Ryan-Palmer We have made some recent updates to the status logic on the Run buttons and we are not seeing this issue on the latest builds. Can you confirm which version of VS you are seeing this in? And does it still happen if you update to the latest?

I'll have a look next time I do a session and report back. I am using VS 2019 Preview and the host is on 2019 vanilla so that may have been an issue. I can't tell you exactly which build we were each using at the time off the top of my head. I'll try to get some more info for you anyways, cheers.

Hi Team!
I'm having some issues with this feature.
I set the Insiders feature but sometimes it works, some times not.
The guests cannot see the unit test in the Test Explorer. Seems that VS doesn't recognize the tests. There is no option to run the tests.
Should I use a specific version of VS2019 or a specific framework?
Does it work with NUnit?
Should I clean some cache?
I'm trying to create Dojo session to train Unit Test and without this feature, it is not possible.
Thank you.

Hi team.
After update to version 16.6.2 of VS 2019 the unit tests are showing in the test explorer again.

Do we need to update to version 16.6.2 to get it running? what are the instructions to get test explorer working through live share?

Also to clarify, is there a way i can see the test explorer stuff in visual studio code?

Official support for the Test Explorer is in VS 2019 16.7+, and all participants will need to have that installed in order for this to work. Let us know if you're running into any problems 馃憤

Regarding VS Code: the Test Explorer UI extension supports Live Share, but it isn't currently interopable with Visual Studio's Test Explorer tool window. That's something we'll explore in the future, once Visual Studio Code adds native support for testing.

In the meanitme, I'm going to close this as resolved since the VS Test Explorer is now supported. If folks have feedback on that feedback, please let us know by filing a new issue. Thanks!

Was this page helpful?
0 / 5 - 0 ratings