Update README.md
Export-NUnitReport function was missing a close tag

Failed test cases weren't closing their failure tag, which resulted in the whole file structure being thrown off.  (test-case elements were being nested inside other test-case elements, etc.)
Merge pull request #195 from dlwyatt/NUnitFix

Export-NUnitReport function was missing a close tag
Update CHANGELOG.md
Upping the version to 3.0.1
Updated version in psd1 file
Fixing wrong version in the manifest, publishing new version so I can update it on Nuget/Chocolatey
Closing conditions of Do/Until and Do/While now ignored by Coverage

These closing conditions aren't triggering their breakpoints for some reason, which was causing false negatives in the coverage output.
Merge pull request #200 from dlwyatt/CoverageLoopFix

Closing conditions of Do/Until and Do/While now ignored by Coverage
Update CHANGELOG.md
Mocking commands that have Dynamic Parameters

This update allows for mocking cmdlets or advanced functions that have dynamic parameters.

There is technically a breaking change from Pester v3.0 in here.  In Pester v3.0, when a mock is defined with the -ModuleName parameter, the MockWith block would be executed within that module's scope.  This has been updated to execute the MockWith block out in the same scope as the test script, since the other scenario is now covered by InModuleScope anyway.

This allows the MockWith block to access variables that were defined out in the test script in all cases, and also cleared up some problems around the new Set-DynamicParameterVariables function while I was working on this branch.
Removing breaking change
Merge pull request #203 from pester/MockingDynamicParameters

Mocking commands that have Dynamic Parameters
Update CHANGELOG.md
Slight cleanup of Get-DynamicParametersForCmdlet code
Slight tweak to avoid PowerShell 3.0 bug

There are some bugs in the PowerShell 3.0 engine which produce "executable script code found in signature block" errors even when there is no signature block.  Interestingly, this bug appears to be triggered when passing a string value to Set-Item in the function provider, but [scriptblock]::Create() works fine (and the resulting script block can be passed to Set-Item just fine.)
Update CHANGELOG.md
Mocking fix

Test-ParameterFilter no longer reconstructs the original mocked command's Param or DynamicParam blocks.  There's no need, since we've already done in that in the bootstrap function and passed along the $PSBoundParameters table anyway.

By reconstructing a basic param block which only contains the parameters that were actually bound, we avoid a problem with evaluating the DynamicParam block outside of the mocked function's original scope.  If that DynamicParam block happened to refer to variables that only exist in a module's scope, it would produce an error.
Merge pull request #206 from dlwyatt/DynamicParamFix

Mocking fix
Still more DynamicParam fixes

To retrieve the dynamic parameters for a function, the code now executes a script block which is bound to the scope of the same module as the mocked function's original location.  This allows the dynamic parameters to be fetched successfully even when they reference script-scoped variables, and the caller is in a different module scope.