Apex Test: DX Project with namespace, cannot open failed test Apex class/code line from the Problems panel

[AndrewStopchenko-SO]

Summary

In a DX Project with namespace, problem entry for a failed Apex test class displays strange "unknown \" location, and clicking the entry opens a blank page rather than the originating Apex test class:

• Same behavior observed on other project (for another namespace).
• Works as expected on a DX Project without a namespace.
• Likely to be related to these issues:
  • Apex Test Sidebar - Does not refresh status when running a test against an org with a namespace #4207
  • When the org is using namespace, the plug-in does not find a Visual Force page #2122

Steps To Reproduce:

1. Open DX Project with namespace. [both projects with the problem are using scratch orgs]
2. Create/update Apex test class to force a test failure.
3. Run unit test from the step 2. Problems panel shows an entry for the failed unit test.
4. Click the problem entry.

Expected result

Opens the Apex class from step 2, highlights the specific code line where the failed assertion is located.

Actual result

Empty file (unknown) is opened instead.

Salesforce Extension Version in VS Code: 62.14.1

Salesforce CLI Version: @salesforce/cli/2.72.21 win32-x64 node-v22.12.0

sf version --verbose --json output:

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.72.21",
  "nodeVersion": "node-v22.12.0",
  "osVersion": "Windows_NT 10.0.19045",
  "rootPath": "C:\\Users\\[USERNAME]\\AppData\\Local\\sf\\client\\2.72.21-6a74781",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.16 (core)",
    "@oclif/plugin-commands 4.1.15 (core)",
    "@oclif/plugin-help 6.2.20 (core)",
    "@oclif/plugin-not-found 3.2.33 (core)",
    "@oclif/plugin-plugins 5.4.24 (core)",
    "@oclif/plugin-search 1.2.17 (core)",
    "@oclif/plugin-update 4.6.21 (core)",
    "@oclif/plugin-version 2.2.19 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.29 (core)",
    "@oclif/plugin-which 3.2.23 (core)",
    "@salesforce/cli 2.72.21 (core)",
    "apex 3.6.8 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.85 (core)",
    "data 4.0.1 (core)",
    "deploy-retrieve 3.17.0 (core)",
    "info 3.4.30 (core)",
    "limits 3.3.43 (core)",
    "marketplace 1.3.7 (core)",
    "org 5.2.16 (core)",
    "packaging 2.9.10 (core)",
    "schema 3.3.45 (core)",
    "settings 2.4.9 (core)",
    "sobject 1.4.48 (core)",
    "telemetry 3.6.29 (core)",
    "templates 56.3.34 (core)",
    "trust 3.7.53 (core)",
    "user 3.6.5 (core)",
    "@salesforce/sfdx-scanner 4.7.0 (user) published 80 days ago (Tue Oct 29 2024) (latest is 4.8.0)"
  ]
}

OS and version: Windows 10 (Windows_NT x64 10.0.19045)

VS Code version: 1.96.4

Most recent version of the extensions where this was working: unknown

[svc-idee-bot]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[svc-idee-bot]

Hello @AndrewStopchenko-SO 👋 It looks like you didn't provide all the required basic info in your issue.

If you haven't already, please provide the following info:
Salesforce Extension Version in VS Code:
Salesforce CLI Version:
OS and version:
VS Code version:
Most recent version of the extensions where this was working:

Here's an example of a set of required info that will pass the validation:
Salesforce Extension Version in VS Code: 60.13.0
Salesforce CLI Version: @salesforce/cli/2.42.6 darwin-arm64 node-v18.18.2
OS and version: MacOS Sonoma 14.5
VS Code version: 1.89.1
Most recent version of the extensions where this was working: 60.11.0

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue, as well as all error messages that you see.
  • A repository that clearly demonstrates the bug is ideal.
  • Error messages can be found in the Problems Tab, Output Tab, and from running Developer: Toggle Developer Tools in the command palette.
• Make sure you've installed the latest version of the Salesforce Extension Pack for VSCode. (docs)
• Search GitHub for existing related issues.

Thank you!

[git2gus]

This issue has been linked to a new work item: W-17624663