PowerShell / PowerShell/PSScriptAnalyzer
Implement PSSA2 testing
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
PSSA2 should be fully tested within reason.
Tests should include:
- xUnit tests of all public engine APIs
- Pester tests of all rules
- Integration tests run on full script examples with rule configurations
- Tests for picking up custom rules
As current default rules are migrated over, their Pester tests should also be migrated over to ensure those rules continue to work as intended.
Where APIs have changed, tests should test for both new and legacy APIs.
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 names no files or entry points, so begin by locating the public engine APIs, rules, full script examples, rule configurations, custom-rule loading, and existing default-rule Pester tests. Run the current xUnit and Pester suites first; done means coverage for new and legacy APIs, integration behavior, custom rules, and migrated default-rule tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100