'Context Default configuration name' test fails on master

[DamonStamper]

Expected Behavior Pester tests performed on Master should not result in test failures.

Current Behavior

Executing script ...\Remotely\Remotely.Tests.ps1

...
Describing ConfigurationName
  Context Default configuration name
    [-] Should connect when a configurationName is specified 87ms
      Expected: {2}
      But was:  {2 2}
      221:             $results | Should Be 2
      at Invoke-LegacyAssertion, C:\Program Files\WindowsPowerShell\Modules\Pester\4.0.8\Functions\Assertions\Should.ps1: line 190
      at <ScriptBlock>, D:\Playground\GitHub\Remotely\main\Remotely\Remotely.Tests.ps1: line 221
  Context Invalid configuration name
...
Tests completed in 6.57s
Tests Passed: 28, Failed: 1, Skipped: 0, Pending: 0, Inconclusive: 0

Steps to Reproduce (in an empty directory)

git clone https://github.com/PowerShell/Remotely.git
cd Remotely
invoke-pester

[DamonStamper]

This issue is blocking pull requests https://github.com/PowerShell/Remotely/pull/19 and https://github.com/PowerShell/Remotely/pull/20