PowerShell / PowerShell/PSScriptAnalyzer
Improve test coverage for `Invoke-ScriptAnalyzer -Settings` argument validation
Open
Nobody has claimed this yet.
Area - Engine
Issue - Enhancement
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
User Story
- As a maintainer of PSScriptAnalyzer
- I want test coverage of the input validation of
Invoke-ScriptAnalyzer -Settingsarguments - so that I can review the stability of changes to this code region.
Specification Details
TODO
PSScriptAnalyzer Version
The latest version of PSScriptAnalyzer as of this writing is 1.18.1.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file or existing test; start by locating the Invoke-ScriptAnalyzer -Settings argument-validation code and its current tests. Define coverage for the Settings inputs, then verify that the test suite exercises the validation behavior and remains passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100