Change:
const viewsService = serviceAccessor.get(IViewsService); const viewContainerLocation = viewDescriptorService.getViewContainerLocation(viewContainer); switch (viewContainerLocation) { <del> case ViewContainerLocation.Sidebar: if (!viewsService.isViewContainerVisible(viewContainer.id) || !layoutService.hasFocus(Parts.SIDEBAR_PART)) { </del> <ins> case ViewContainerLocation.AuxiliaryBar: case ViewContainerLocation.Sidebar: { const part = viewContainerLocation === ViewContainerLocation.Sidebar ? Parts.SIDEBAR_PART : Parts.AUXILIARYBAR_PART; if (!viewsService.isViewContainerVisible(viewContainer.id) || !layoutService.hasFocus(part)) { </ins> await viewsService.openViewContainer(viewContainer.id, true); } else { editorGroupService.activeGroup.focus(); } break; <ins> } </ins> case ViewContainerLocation.Panel: if (!viewsService.isViewContainerVisible(viewContainer.id) || !layoutService.hasFocus(Parts.PANEL_PART)) { await viewsService.openViewContainer(viewContainer.id, true);

Discussion:
Type: <bBug</bAt some point recently the "view" -"testing" menu stopped opening the testing view. The menu item is present but clicking it has no observable effect. Additionally, the option is no longer available in the activity bar on the left. Note that it's not simply hidden. It's also missing from the context menu to show / hide items as well. This was working up until a few days ago. What does work is the command pallette. I can see from the logs that the extension is loaded, and by typing "testing" into the command pallette, I can still open the view, and from there on it functions normally. VS Code version: Code 1.74.2 (Universal) (, 2022-12-20T10:26:09.430Z) OS version: Darwin arm64 22.2.0 Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (46)</summaryExtensionVersion ------ better-comments3.0.2 aws-toolkit-vscode1.60.0 better-tests0.3.1 atlascode2.10.12 emmet-jss1.0.0 path-intellisense2.8.4 dart-code3.56.0 flutter3.56.0 vscode-markdownlint0.48.1 vscode-eslint2.2.6 githistory0.6.19 xml2.5.1 gitlens13.2.0 prettier-vscode9.10.3 vscode-pull-request-github0.56.0 go0.37.0 rest-client0.25.1 git-graph1.30.0 dotenv1.0.1 djlint2022.10.1 vscode-docker1.23.3 isort2022.8.0 python2022.20.1 vscode-pylance2022.12.20 jupyter2022.11.

jupyter-keymap1.0.0 jupyter-renderers1.0.12 vscode-jupyter-cell-tags0.1.6 vscode-jupyter-slideshow0.1.5 remote-containers0.266.1 cmake-tools1.12.27 cpptools1.13.8 cpptools-extension-pack1.3.0 vsliveshare1.0.5788 awesome-flutter-snippets4.0.1 printcode3.0.0 material-icon-theme4.23.0 gotestexplorer0.1.13 vscode-yaml1.10.1 LiveServer5.7.9 pdf1.2.2 cmake0.0.17 alphabetical-sorter2.0.1 vscode-maven0.40.2 JavaScriptSnippets1.8.0 markdown-all-in-one3.5.0 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Which extension is providing this? Maybe it isn't activating successfully. The Extension Host channel of the Output tab may reveal something.
Technically, this isn't an extension. It's the built in testing support. I think it's this feature:
/gifPlease
Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, files are preferred as they are displayed inline on GitHub. You may find helpful as a browser-based gif recording tool. If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording ( in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue. Happy coding!
Hi, I'm helping Iris look into the issue. Here's a video of what we're seeing. "testing" should show in the activity bar and in the context menu at the start of the recording but isn't listed. But the functionality that it should point at is still accessible via the command pallet, shown later in the video. !
That is because you moved the Testing view into the secondary sidebar. It therefore does not appear in the context menu on the primary sidebar.

You can reset its location by dragging the beaker icon back into the primary sidebar, or using the command.
fyi if we want to make view location stuff more clear here
there seems to be a bug still with the Testing main menu entry. It should open the view wherever it is. Repro: testing container to secondary side bar secondary side bar View Testing =no response
Oh, right, I was just going off the last screencap. That's strange, but should be fixable...