0 failed to be found in array

[vors]

Describe foo {
    It "should find 0 in range" {
        0 | Should be @(0..2)
    }

    It "should find 1 in range" {
        1 | Should be @(0..2)
    }

    It "should find 2 in range" {
        2 | Should be @(0..2)
    }
}

[dlwyatt]

That's interesting, but we can't fix this and #246 at the time time; this $scalar | Should Be $array behavior is always going to fail once #246 is done.

[vors]

Yeah, that's fine. The reason why I use such syntax now:
https://github.com/SublimeText/PowerShell/blob/dev/tests/pester/Syntax.Tests.ps1#L65

Maybe it make sense to add syntax for range comparison, like

$errorCount | Should be in (0..2)

Of course, I can use something like

(0..2) -contains $errorCount | Should be $true

but then I loose context on failure.

[dlwyatt]

In the short term, here's a goofy workaround:

0 | Should Be @(0;0..2)

By sticking an extra 0 element into the array, it causes the $array -eq $scalar expression to return a 2-element array instead of a single-element array. This evaluates to $true no matter what's in the array (where a single-element array's boolean evaluation depends on what's in the array; 0 is $false.)

[dlwyatt]

Of course, I can use something like
(0..2) -contains $errorCount | Should be $true
but then I loose context on failure.

Just curious: with the changes that are getting added in #266 , would you still want to see a "BeIn" operator, or would you use the Should Be $true option with your own logic?

[vors]

I think with #266 there is no need in BeIn. This bug is just an observation of existing inconsistency. With fix for #246 it should gone.