Pester should report tests failure if there is syntax error?

[xinhuang]

Now if there is an syntax error, e.g. misspelled words, missing closing curly brace, pester will yield an error while loading the script, but later in the test report, result is still green.

I'm using Jenkins to scheduled run all tests, and use Jenkins job status to monitor test result. But if there's syntax error, I'm expecting the job to be red, rather later examine the xUnit plugin report and find out some tests are missing.

I'd like to propose 2 solutions:

1. Mark one test failure of every script error. This is the simplest to do.
2. Mark result as failed, but calculate how many Its in failed script, to roughly calculate the number of failing test.

@scottmuc what do you think?

[scottmuc]

Personally, I think a fast fail is preferred. Pester doesn't have much design in the sense that it simply executes each script as it sees them. Counting the number of syntax errors probably isn't needed.

I appreciate you looking at making Pester better!

[xinhuang]

Because we are now using PowerShell as our glue script language for build. Its on the critical path to our whole system, and the whole team is just start learning to use PowerShell. If the transition can be smooth work won't be so tiring. :P

Chinese New Year vacation is approaching, so I guess I will submit a PR during the vacation.

Thanks for your reply!

[scottmuc]

Cool! You may want to check out http://ydeliver.stacktoheap.com/ as well (for .Net project builds). Disclaimer, I did have a part with developing a bit of it.

If you have any other questions related to Pester, please join the google group: https://groups.google.com/forum/#!forum/pester

[dlwyatt]

Resolved in the upcoming v3.0 release.