You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run Invoke-DscResourceTest at clean environment, this error occured:
PS C:\> Invoke-DscResourceTest
Unable to find type [Pester.OutputTypes].
At C:\Program Files\WindowsPowerShell\Modules\DscResource.Test\0.16.0\DscResource.Test.psm1:1628 char:9
+ [Pester.OutputTypes]
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (Pester.OutputTypes:TypeName) [], RuntimeException
+ FullyQualifiedErrorId : TypeNotFound
Problem resolved by running this command before use Invoke-DscResourceTest:
PS C:> New-PesterConfiguration
Run : Run configuration.
Filter : Filter configuration
CodeCoverage : CodeCoverage configuration.
TestResult : TestResult configuration.
Should : Should configuration.
Debug : Debug configuration for Pester. ⚠ Use at your own risk!
Output : Output configuration
TestDrive : TestDrive configuration.
TestRegistry : TestRegistry configuration.
PS C:\> Invoke-DscResourceTest
cmdlet Invoke-DscResourceTest at command pipeline position 1
Supply values for the following parameters:
ProjectPath:
Please, update documentation.
The text was updated successfully, but these errors were encountered:
Hmm... Looking at the code the type is in the parameters, so my suggestion above won't work. So we need to update the documentation as suggested telling the user to import the module Pester prior to invoking the command.
Though, I see there is code to handle Pester 4, but will this work with Pester 4 when that type exist in the parameters... maybe the type exist i Pester 4 as well... 🤔
When I run Invoke-DscResourceTest at clean environment, this error occured:
Problem resolved by running this command before use Invoke-DscResourceTest:
PS C:> New-PesterConfiguration
Please, update documentation.
The text was updated successfully, but these errors were encountered: