dsccommunity / dsccommunity/DscResource.Test

README.md additition

Open
#119 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation help wanted
Dominant language
PowerShell
Stars
6
Forks
9
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Update README.md using the reported clean-environment reproduction: run Invoke-DscResourceTest and note the [Pester.OutputTypes] error, then run New-PesterConfiguration before invoking it again. Document the workaround and the expected ProjectPath prompt shown in the issue; no test file is mentioned.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.