[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rules when given glob with recurse switch 75ms (73ms|2ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rules when given glob with recurse switch 22ms (21ms|1ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rules when given recurse switch 20ms (18ms|1ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rules when given a glob 40ms (38ms|2ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rule when given a rule folder path 37ms (35ms|2ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rule 23ms (23ms|1ms)

[-] Test importing customized rules with null return results.Test Invoke-ScriptAnalyzer with customized rules.will not terminate the engine 36ms (34ms|2ms)

[-] Test importing customized rules with null return results.Test Get-ScriptAnalyzer with customized rules.will not terminate the engine 43ms (43ms|1ms)

[-] Correction Extent.Object construction.creates the object with correct properties 4ms (3ms|1ms)

[-] Discovery in /Users/runner/work/PSScriptAnalyzer/PSScriptAnalyzer/Tests/Engine/ModuleHelp.Tests.ps1 failed with:

The strategy configuration was canceled because "ci.macos-latest" failed

The strategy configuration was canceled because "ci.macos-latest" failed

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rules when given glob with recurse switch 153ms (150ms|3ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rules when given recurse switch 147ms (145ms|3ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rules when given a glob 168ms (165ms|3ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rule when given a rule folder path with trailing backslash 152ms (149ms|3ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rule when given a rule folder path 168ms (165ms|3ms)

[-] Test importing correct customized rules.Test Get-ScriptAnalyzer with customized rules.will show the custom rule 161ms (160ms|1ms)

[-] Test importing customized rules with null return results.Test Invoke-ScriptAnalyzer with customized rules.will not terminate the engine 168ms (166ms|2ms)

[-] Test importing customized rules with null return results.Test Get-ScriptAnalyzer with customized rules.will not terminate the engine 171ms (169ms|1ms)

[-] Correction Extent.Object construction.creates the object with correct properties 21ms (19ms|2ms)

[-] Discovery in D:\a\PSScriptAnalyzer\PSScriptAnalyzer\Tests\Engine\ModuleHelp.Tests.ps1 failed with:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No files were found with the provided path: testResults.xml. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/