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

Allow sharing terminals that are created by extensions (e.g. test runner CodeLens) #123

Closed
jtleaming opened this issue Mar 5, 2018 · 5 comments

Comments

@jtleaming
Copy link

Product and Version [VS/VSCode]: VS Code Insiders
OS Version [macOS/Windows]: Windows
Live Share Extension Version: Current
Target Platform or Language [e.g. Node.js]:

Steps to Reproduce / Scenario:

Running debugger shares debug output, but test runner does not share test output. It would be nice if test runner could be shared as well, so both participants can view test results.

@lostintangent
Copy link
Member

@jtleaming Thanks for the suggestion! Just to make sure we understand your current workflow, could you clarify how you’re currently running your tests? Are you running a command in the integrated terminal? Using an extension (e.g. the Java Test Runner)? Using a tasks.json task?

@jtleaming
Copy link
Author

We were running the tests from within the IDE. So these were dotnet tests using the xunit runner. Co-running from the terminal would also be useful.

@lostintangent
Copy link
Member

lostintangent commented Mar 6, 2018

@jtleaming Just to confirm: are you running these tests in VS Code using the run test CodeLens that the C# extension contributes (like below)?

screen shot 2018-03-05 at 4 51 14 pm

We've got a feature request tracking the ability to share a terminal session, which would allow the host to share a terminal, run a test command (dotnet test?) and then all participants would be able to see it.

Additionally, we've got a feature request tracking the ability for guests to run task.json tasks remotely, which could include a "test" task.

However, you bring up a great point that there are other arbitrary ways to automate actions/commands in VS Code, which in turn, generate output windows (e.g. test output). And so, we can use this issue to track that use case.

@jtleaming
Copy link
Author

Thanks for the clarification, I wasn't sure what to call this. But yes, the run test CodeLens.

@lostintangent lostintangent changed the title Shared test runner Allow sharing terminals that are created by extensions (e.g. test runner CodeLens) May 8, 2018
@lostintangent
Copy link
Member

This has now been addressed in the latest Live Share release 🔥 Check out the release notes for more details. Thanks again for the feedback here 👍

Chuxel pushed a commit that referenced this issue Feb 17, 2019
…s://github.com/microsoftdocs/live-share (branch master) (#123)

* docs: typo fix (#1646)

@@ line 367
old:
```simply needs to hare state button```

@@ line 367
new: ```needs to click the share / session```

* Adding user profile entry to ToC

* fix: docs/reference/manual-join.md (#1697)

- Adjust heading levels not to skip
- joinign -> joining
- indentify -> identify

* fix: Add code fence language to JSON examples (#1692)

* fix: docs/reference/platform-support.md (#1698)

- Double word "the"
- Double word "features"
- Use https for links
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

3 participants