Errors reported from Describe and Context blocks

[dlwyatt]

Quick update to make terminating errors that occur in a Describe or Context block cause a failed "test" to appear in the output.

Because we're just piggybacking onto the existing PesterState.AddTestResult and Write-PesterResult code, the output looks as though it came from an It statement, though the name is always "Error occurred in Context block" or "Error occurred in Describe block". If this style of output is undesirable, a more extensive code update would be required.

Do we need to handle nonterminating errors in this fashion as well, or leave that up to the person writing the test script? (For instance, they can set -ErrorAction Stop, if they like.)

This is intended to fix issue #79

[dlwyatt]

Quick note: I don't think this PR will be merged as-is. I just put it up as a starting point for us to discuss in issue 79's thread. Expect more commits to be added here as we figure out what the behavior should be.

[dlwyatt]

This branch produces failed tests when a test script contains a syntax error, or when terminating errors are produced from inside Describe or Context blocks (but not inside an It block.) These failed tests become part of the output via the console, NUnit XML file, exit code and PassThru features, allowing a CI solution to detect the error condition not to treat the test suite as "passed".

[dlwyatt]

In addition to issue 79, this also takes care of #91.

[mzs-github]

Do we need to handle nonterminating errors in this fashion as well, or leave that up to the person writing the test script? (For instance, they can set -ErrorAction Stop, if they like.)

It's funny you should mention that - the error I was thinking about when I commented earlier was actually a nonterminating error and I'd forgotten to set $ErrorActionPreference in my test script. I wonder if it would make sense to add $ErrorActionPreference = 'Stop' and maybe a strict mode setting to the top of the generated fixtures and/or the examples in the Wiki.