Running tests for PR #1912

[alerickson]

PR Summary

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[alerickson]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

🔵 Needs a closer look

There is a confirmed null-dereference in GetPathsFromEnvVarAndScope when scope is null, which can cause runtime failure.

Pull request overview

This PR updates PSResourceGet’s user-scope install/search path resolution to prefer PowerShell’s $PSUserContentPath (with legacy fallbacks) and adds end-to-end coverage to validate the resolved install locations.

Changes:

• Update Utils.GetStandardPlatformPaths to resolve the current-user base path via $PSUserContentPath, falling back to legacy paths when unavailable.
• Add internal test hooks to capture the last-resolved user content path and its source.
• Add Pester end-to-end tests validating CurrentUser vs AllUsers installation locations and the $PSUserContentPath/legacy selection behavior.

File summaries

File	Description
test/PSContentPath.Tests.ps1	Adds end-to-end Pester coverage around user content path selection and install locations.
src/code/Utils.cs	Switches current-user base directory resolution to $PSUserContentPath with legacy fallback and verbose tracing.
src/code/InternalHooks.cs	Adds hook fields + helper methods for testing the resolved content path/source.

Review details

Suppressed comments (1)

src/code/Utils.cs:1116

• GetPathsFromEnvVarAndScope claims to support scope being null (see the scope is null check), but it still dereferences scope.Value when adding AllUsers paths. If scope is actually null, this will throw a NullReferenceException and also prevents returning the AllUsers paths when scope is omitted.

            List<string> resourcePaths = new List<string>();
            if (scope is null || scope.Value is ScopeType.CurrentUser)
            {
                resourcePaths.Add(Path.Combine(psUserContentPath, "Modules"));
                resourcePaths.Add(Path.Combine(psUserContentPath, "Scripts"));
            }

            if (scope.Value is ScopeType.AllUsers)
            {
                resourcePaths.Add(Path.Combine(programFilesPath, "Modules"));

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[alerickson]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).