larssb commented 7 years ago

Description

Fixed the combination of using the OVF -TestFilePath parameter with invoke-pester -quiet or -show. The code, when using the -TestFilePath parameter did not take into consideration the version of Pester and therefore the warning about -Quiet.

While running the Pester tests. Several tests failed as I was using a user through "Runas" while in a Windows user session that is a non-admin user. The "Runas" user does not have IE configured in its profile and therefore the invoke-webrequest cmdlet fails without the -UseBasicParsing parameter. I added that to several tests to avoid this error. Shouldn't be an issue as it is very simple requests via that is tried with invoke-webrequest.

Related Issue

28

Motivation and Context

To get rid of an unnecessary warning. That is already fixed for other parameters in OVF.

How Has This Been Tested?

Ran invoke-operationvalidation on actual tests on MacOS and thereby PowerShell core Beta v8.
Executed all the Pester tests provided in the repo.

Screenshots (if appropriate):

Types of changes

[ X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes. <-- I think the current tests already covers.
[ X] All new and existing tests passed.

This change is