Description
The Test Explorer view in Cursor IDE (VSCode’s “Testing” view) is not easily accessible as it lacks a dedicated icon in the activity bar. While the view can be accessed through the command palette (ctrl+shift+p) by searching for “Testing: Focus on Test Explorer View”, there is no way to pin this view for quick access.
Current Behavior
-
Test Explorer view is only accessible through command palette
-
No dedicated icon in activity bar
-
View cannot be pinned
-
Inconsistent naming between VSCode (“Testing”) and Cursor (“Test Explorer”)
Expected Behavior
-
Test Explorer view should have a dedicated icon in the activity bar
-
View should be pinnable like other views
-
Consistent naming with VSCode’s “Testing” view
Workaround
Currently, users must:
-
Use ctrl+shift+p
-
Type “Testing: Focus on Test Explorer View”
-
Click the command to access the view
Environment
-
Version: 0.48.8 (user setup)
-
VSCode Version: 1.96.2
-
Commit: 7801■■■6824585b7f2721900066bc87c4a09b740
-
Date: 2025-04-07T20:02:01.084Z
-
Electron: 34.3.4
-
Chromium: 132.0.6834.210
-
Node.js: 20.18.3
-
V8: 13.2.152.41-electron.0
-
OS: Windows_NT x64 10.0.19045
-
Python Environment: Configured in workspace settings
-
Testing Framework: pytest
Installed Extensions
-
DavidAnson.vscode-markdownlint
-
ms-python.python
-
ms-python.vscode-pylance
-
ms-toolsai.jupyter
-
hbenl.vscode-test-explorer
-
mhutchie.git-graph
-
ms-python.pylint
Additional Context
The workspace is configured with proper testing settings:
{
"python.testing.pytestEnabled": true,
"python.testing.autoTestDiscoverOnSaveEnabled": true,
"testExplorer.addToEditorContextMenu": true,
"testing.coverageToolbarEnabled": true,
"testing.showCoverageInExplorer": true
}
Impact
This issue affects developer productivity by making test navigation and management more cumbersome than necessary.
Suggested Fix
-
Add a dedicated Test Explorer icon to the activity bar
-
OR rename the view back to “Testing” to match VSCode’s convention
-
Add ability to pin the Test Explorer view
-
Ensure consistent naming between VSCode and Cursor
Priority
Medium - Affects developer workflow but has a workaround