Justin Grote

@dfinke they support themes so there's an API to do the work that @bobbynog basically did above, but, as you said, the license change would make it difficult to adopt...

@fflaten @nohwnd please review

@fflaten @nohwnd ready for re-review. I strong typed the result object for all Should results, and kept the info in the TargetObject without exposing it outwardly. Plugins should still be...

@fflaten @nohwnd The strong typing already showed me that `Should -Invoke` is actually defined in Mock and not in its own assertion, and was emitting pscustomobjects from there. There's also...

I dropped the `CreateShouldErrorRecord` method back to object (34b47445f3dc2b826a786e74f4f6151c7de691b5) but all builtin items will still use the result type and I'll also fix up the shouldInvoke output as well to...

@nohwnd thank you!

``` ~\\Sandbox\Pesterinvoke-pester -ExcludePath C:\Users\jgrote\Projects\Sandbox\Pester\ExcludeMe -Output Diagnostic Discovery: Starting test discovery in 2 test containers. Starting discovery in 2 files. Discovery: Discovering tests in C:\Users\jgrote\Projects\Sandbox\Pester\ExcludeMe\ExcludeMe.Tests.ps1 Discovering in C:\Users\jgrote\Projects\Sandbox\Pester\ExcludeMe\ExcludeMe.Tests.ps1. Found 1 tests....

I like this thinking, I don't see the edge cases as long as you check if it's a directory first. Even with a lot of files this is very efficient...

I dont think we need yet another dot file, especially because you could do this yourself with Get-Content and don't require pester to do it for you.

> Would love to see this feature, our build times are getting longer as we keeping adding tests for new powershell code. As a workaround, if your tests are not...