Deepak Singh Dhami

@sathya-bhat I gave this a shot in my setup and indeed this fails if the switch type is changed as you mentioned. The interesting thing which I noticed is that...

I would vote for the second one, since I have hardly seen VMSwitches with same name and different switch type being used. Also the idea of DSC fixing the configuration...

Good question. At the moment the Start-RemotelyJobProcessing Function (under Private\Helper.ps1) handles processing of these jobs, based on the current logic there is no timeout. It simply waits for the jobs...

Pushing this to the next release with classes.

Started cleaning some of the old tests I have for some functions and adding them. Open to accepting more PRs for adding unit tests and learn few things :)

Far from complete.

Now that you mention it, maybe it is not required. These are from the time where I thought that we could install modules on the system itself rather than copying...

Also adding the ability to connect to a specific PSRemoting endpoint (JEA endpoint #4 ) would fall in place with this.

Thinking aloud. Should PSRemotely support passing tags at two different scopes? ## At Node scope This would capability to organize tests targeting the same nodes. ```powershell PSRemotely { Node AD...

Or we can add a parameter named -PesterSplatHash which takes a hashtable and splats that to the Invoke-Pester on the PSRemotely node while running the tests. This is much cleaner...