Skip to content
This repository has been archived by the owner on Dec 8, 2021. It is now read-only.

'Context Default configuration name' test fails on master #21

Open
DamonStamper opened this issue Nov 28, 2017 · 1 comment
Open

'Context Default configuration name' test fails on master #21

DamonStamper opened this issue Nov 28, 2017 · 1 comment

Comments

@DamonStamper
Copy link

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
Copy link
Author

DamonStamper commented Nov 29, 2017

This issue is blocking pull requests #19 and #20

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant