mrboring

@dlwyatt So, in my test code it is possible to set PSBreakpionts on lines 7 and 12. I've done so in testing. Are the `throw` and `continue` keywords not covered?

@dlwyatt Thanks for the explanation, very helpful!

@dlwyatt, @nohwnd I've had a quick look at the source and wonder if the following change would be valid. #### Function: Coverage.ps1\Get-CommandsInFile Line: 195 before ```PowerShell $predicate = { $args[0]...

@nohwnd I'm in the process of testing the code. I've found an issue with the `return` keyword. It is not being detected as hit. So I've been looking through the...

@nohwnd As you pointed out, when the column is specified the breakpoint is not hit. When it's not specified the breakpoint is hit. So, this looks like a PowerShell issue....

@nohwnd After a bit of further investigation, based on your sample code: - If I wrap the `return` statement in an if block, the breakpoint is not hit. - If...

I'm having the same issue. I also get it with only a single message. If I click another tab (Headers, Body, Sections or Raw) then click back on the Message...

I have the same issue. Need to press space then delete the space to get syntax highlighting to kick in. UPDATE: I also get this issue when opening a folder...

Can I suggest that the values are hard-coded to get around this. The code below has the minimal changes to get it to work: ```F# open System.IO open FsExcel open...

I think I have another example of this issue in Pester tests. The code below is based on actual code, but simplified as much as possible. Expected behavior ------------------ No...