File tree Expand file tree Collapse file tree 1 file changed +2
-1
lines changed
Expand file tree Collapse file tree 1 file changed +2
-1
lines changed Original file line number Diff line number Diff line change @@ -8,7 +8,7 @@ PSScriptAnalyzer is shipped with a collection of built-in rules that checks vari
88PSScriptAnalyzer cmdlets
99======================
1010```
11- Get-ScriptAnalyzerRule [-CustomizedRulePath <string[]>] [-Name <string[]>] [<CommonParameters>]
11+ Get-ScriptAnalyzerRule [-CustomizedRulePath <string[]>] [-Name <string[]>] [<CommonParameters>] [-Severity <string[]>]
1212
1313Invoke-ScriptAnalyzer [-Path] <string> [-CustomizedRulePath <string[]>] [-ExcludeRule <string[]>] [-IncludeRule <string[]>] [-Severity <string[]>] [-Recurse] [<CommonParameters>]
1414```
@@ -46,6 +46,7 @@ Pester-based ScriptAnalyzer Tests are located in ```<branch>/PSScriptAnalyzer/Te
4646.\InvokeScriptAnalyzer.tests.ps1
4747* Run Tests for Built-in rules:
4848.\* .ps1 (Example - .\ AvoidConvertToSecureStringWithPlainText.ps1)
49+ You can also run all tests under \Engine or \Rules by calling Invoke-Pester in the Engine/Rules directory.
4950
5051
5152Contributing to ScriptAnalyzer
You can’t perform that action at this time.
0 commit comments