Live-share: Support guests to see continuous/live test results in the editor (NCrunch, Wallaby.js)

Created on 7 Mar 2018  路  3Comments  路  Source: MicrosoftDocs/live-share

Product and Version: VS
OS Version: Windows
Live Share Extension Version: 0.2.133.57639
Target Platform or Language: C#/NCrunch

In order to support mob programming with TDD it would be useful to display the ncrunch test coverage results (green/red/white dots) alongside the code being viewed by the guests. Currently there is no feedback around passing or failing tests for the guests.

extensions testing feature-request product-feedback vs vscode

Most helpful comment

This could also be a use case for providing an API / SDK re: #88

Although, that would require NCrunch people to use / deal with the API themselves...

Without having any knowledge about Visual Studio Extension development... I presume (probably not? 馃槂) that to allow this, Live Share would have some sort of hooks into the VS Extension SDK to allow replicating the _state_ (SDK state) of the host, to replicate it to the guest(s) (hopefully that makes sense).

So basically, make sure that both host and guests have NCrunch / Wallaby.js ... I think trying to make it so only the host has the live testing extension could lead to all sorts of issues (re: Licensing of the extensions to say the least) 馃槂

All 3 comments

@lockoncode Thanks for this suggestion! This definitely makes a lot of sense for pair/mob programming, and is a scenario we鈥檇 like to eventually support. There are other continuous/live testing extensions (e.g. Wallaby.js) that would have similar problems, so we can use this issue to track the general use case.

This could also be a use case for providing an API / SDK re: #88

Although, that would require NCrunch people to use / deal with the API themselves...

Without having any knowledge about Visual Studio Extension development... I presume (probably not? 馃槂) that to allow this, Live Share would have some sort of hooks into the VS Extension SDK to allow replicating the _state_ (SDK state) of the host, to replicate it to the guest(s) (hopefully that makes sense).

So basically, make sure that both host and guests have NCrunch / Wallaby.js ... I think trying to make it so only the host has the live testing extension could lead to all sorts of issues (re: Licensing of the extensions to say the least) 馃槂

@worzeel That is exactly right! #88 is meant to track the scenario of Live Share enabling arbitrary extensions to synchronize their own custom state. Continuous testing experiences would benefit from that capability, and is a scenario that I鈥檇 love to explore at some point.

As you mentioned, that would require extension authors to do some work, but we hope that Live Share is a compelling enough scenario that some folks would be interested in working with us to make their experiences collaborative 馃槃

Was this page helpful?
0 / 5 - 0 ratings