Add ability to override Pester script parameters and specify version of module to execute

[devblackops]

This PR adds the ability to pass script parameters to Pester tests referenced in issue #6 as well as the ability to specify the version of the module to execute in the event that there are multiple versions of the OVF module in $PSModulePath.

If a Pester script inside an OVF module had a parameter block like so:

param(
    [int]$SomeValue = 100
    [bool]$ExtraChecks = $false
)

Describe 'foo' {
    Context 'bar' {
        ...
    }
}

then those parameters can be overridden by injecting new values in the form of a [hashtable] when calling Invoke-OperationValidation

Example

Invoke-OperationValidation -ModuleName MyModule -Overrides @{ SomeValue = 50; ExtraChecks = $true }

---

This change is

[msftclas]

Hi @devblackops, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

[msftclas]

@devblackops, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, MSBOT;

[devblackops]

@JamesWTruher Any comment on this PR?

[devblackops]

@JamesWTruher Who at Microsoft is responsible for maintaining this module? Is it just you or are there others that can take a look at this? I'd like to see some traction or PR review. This is a super useful module but if it takes ages to get a PR through or even to get a discussion going, I don't see it going anywhere.

[ngetchell]

Some feedback on this PR would be nice. This is something I'd use heavily if implemented.

As I invest more time into OVF I'd like to know there is active development behind it.

[ngetchell]

After speaking with @devblackops he mentioned that this PR adds tag support. I haven't tried his implementation out yet but I'm excited. The Simple/Comprehensive designation seemed arbitrary. Being able to use my own tags from Pester to better categorize my OVF tests would be great.

[devblackops]

Small clarification. This PR does NOT add tag support. Just support for providing parameters to Pester scripts and OVF module versions. Tag support is in this branch in my fork. That branch includes the changes in this PR as well. Once I do a little more testing, I'll submit a PR to add tag support. That is, if anyone at Microsoft will review and comment 😏

[JamesWTruher]

sorry about the delay, I'm not getting notifications for some reason. I like this PR, but could we add some tests to validate the new functionality?

[JamesWTruher]

$modDir [](start = 102, length = 7)

when I see write things like this, i usually like to use "${modDir}.psd1" just to avoid confusion

[devblackops]

Indeed. I've changed it to "$($obj.prop)" syntax

[devblackops]

Thanks for responding @JamesWTruher. I'll make the required changes to tests and let you know when this can be reviewed again.

Expect a similar PR to come in that adds tag support referenced in #10

[devblackops]

Hi @JamesWTruher
I tweeked some minor things and added a few tests to validate script parameters can be overridden. This also handles a change in Pester 4.0 behavior as the -Quiet parameter is deprecated now.

I believe this is ready to merge.

Cheers.

[JamesWTruher]

thanks!