Test Explorer not working in some workspace

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m using the GO extension which has Test support included. The Test Explorer works in many workspaces. But in one workspace, it is not shown.

Steps to Reproduce

Open a specific workspace.
The Test Explorer is not shown.
Press ctrl+shift+p, then search Test Explorer. No result is found.
Open a new cursor instance, open a workspace that Test Explorer works.
Press ctrl+shift+p, then search Test Explorer. select Testing: Focus on Test Explorer View. The command works normally.
Go back to the old not-working instance. Press ctrl+shift+p, the Testing: Focus on Test Explorer View shows in the first position in the history. Select it. Then the Test Explorer shows and does discover test cases in the workspace.

Operating System

Linux

Version Information

Version: 3.1.15
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.19.12-200.fc43.x86_64

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey! This is likely expected VS Code behavior rather than a Cursor bug. The Testing view container uses hideIfEmpty: true, so the Test Explorer icon only appears in the sidebar once a testing extension, in your case, the Go extension, actively discovers and registers tests in the current workspace.

A quick question to confirm: does the workspace where Test Explorer is missing actually contain Go tests? Specifically:

  • Is there a go.mod at or near the workspace root?
  • Are there any *_test.go files the Go extension can discover?
7

Answer to both the questions: Yes

8

Thanks @mm_team90!

So far, I haven’t been able to reproduce the issue. There might be something specific about the project you’re working with. Would you be able to create a minimal reproducer of a project that exhibits this behavior?