Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Group test explorer test by workspace in multi-root workspace

See original GitHub issue

I am using the multi-root workspace in vs code to open multiple python packages, each with their own tests folder containing the tests for that package. The test explorer displays all tests, but does not group them by the workspace they come from. For a simple multi-root workspace with just two packages, this looks like the following screenshot:

Since all folders are named in the same way, its cumbersome to determine which entry is from which workspace.

I also searched through the extension’s settings, but didn’t find anyting related.

I think the best solution would be to group the tests simililarly as in the repositories in the source control view. What do you think?

Issue Analytics

State:
Created 9 months ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

brettcannoncommented, Dec 14, 2022

Ideally a multi-root workspace would have one more level of hierarchy per workspace at the top of the tree. Otherwise I would consider it all the same as if it was a single-root workspace.

0reactions

eleanorjboydcommented, Dec 14, 2022

@brettcannon and @luabud what is the desired workflow do you think in this case? Since it requires a step to discover tests in each workspace should a multi-root workspace have the workspace listed on discovering tests for a single workspace or just for discovering more than one workspace? Additionally should the workspace be displayed the same way as a folder is (so above tests in this given example with tests nested under)? The final implementation question to consider is the 3 buttons, run, run in debug mode, and go to file and what these buttons should do given it is in reference to a workspace instead of a file. I think it can behave pretty much the same given workspaces still have paths with which we could direct to or run tests in. Thanks and let me know if you have opinions on the matter.

Top Results From Across the Web

Multi-root Workspaces in Visual Studio Code

You can open and work on multiple project folders in Visual Studio Code with multi-root workspaces.

Work with multiple AL project folders within one workspace

Visual Studio Code offers the multi-root workspace feature, which enables grouping different project folders into one workspace.

Visual Studio Code tips for monorepo development with Multi ...

A multi-root workspace is a feature in Visual Studio Code where you can have multiple root folders in one explorer view.

python - Use unit tests for a single project when I have multiple ...

Could you select pytest instead of unittest search? "python.testing.pytestEnabled": true, "python.testing.pytestArgs": ["."].

testing – James Pearson

Using the Test Explorer is pretty self-explanatory if you've already been using AL Test Runner. When you open your workspace/folder the tests should...