Repository navigation
Add tests for NanoServer and IoT for the debugging support to step in "Invoke-Command -ComputerName" #3236
Description
This is a follow-up issue for PR #3015. There are 2 open comments left in the PR, both are about the test file added in the PR (test/powershell/engine/Remoting/InvokeCommandRemoteDebug.Tests.ps1):
- Comments about validating this feature on NanoServer and IoT and add (or skip if needed) the tests when running on NanoServer/IoT.
- Comments about the
DummyHostimplementation in the test.
The PR has been merged, and this follow-up issue can be addressed separately.
Activity
iSazonov commentedon Aug 29, 2018
If MSFT team migrate tests to VS Team Services the issue must be taken into account.
/cc Travis Plunk (@TravisEz13)
TravisEz13 commentedon Aug 29, 2018
Ilya (@iSazonov) Why is the Migration to VSTS relevant here?
iSazonov commentedon Aug 29, 2018
Travis Plunk (@TravisEz13) I hope we'll can able to get VMs with full set platforms and versions (including IoT, Core, Server ...) and to implement remoting tests.
TravisEz13 commentedon Aug 29, 2018
Ahh, with VSTS we should be able to test with nanoserver and windowsservercore containers. Getting VMs would cost money for the times we keep them running.
TravisEz13 commentedon Aug 29, 2018
Technically we can do this with AppVeyor, but... it's more complicated.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.