Wrong line number is reported if fails not in main script file about pester

[mwrock]

Fixed in 6c4b25e. It.ps1 now searches the stack trace for the current script and then parses the line number.

[AndrewSav]

The line numbers is still out of wack in the latest nuget version.
bla.Tests.ps1:

$here = Split-Path -Parent $MyInvocation.MyCommand.Path
    $sut = (Split-Path -Leaf $MyInvocation.MyCommand.Path).Replace(".Tests.", ".")
    . "$here\$sut"

    Describe "bla" {

        It "does something useful" {
            Expect-Result $true $false "Stone flied"
        }
    }

bla.ps1:

# Empty
# Empty
# Empty
# Empty
# Empty
# Empty
# Empty
# Empty
# Empty
# Empty

function Expect-Result($expected, $actual, $text) {
    $actual | Should Be $expected
}

run pester, output is:

Executing all tests in C:\Andrew\pp\new-fixture
Describing bla
[-]   does something useful 192ms
   Expected: {True}, But was {False}
   at line: 18 in C:\Andrew\pp\new-fixture\bla.Tests.ps1
Tests completed in 192ms
Passed: 0 Failed: 1

The line number is apparently wrong.

[AndrewSav]

Opened new issue 80, since I don't know if github tracks old issues. Please merge, delete/re-open etc as appropriate. #80