microsoft / microsoft/vscode-dotnettools

[SUGGESTION] Test Explorer is able to be grouped

Open
#935 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-test enhancement
Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Description

Describe the feature you'd like

Im basing the Feature Request from what I see in Visual Studio 2022, where there are many additional option to group your tests into.
image

Benefits
  1. Improved Organization: It helps keep your tests neatly organized and easy to locate. This can be particularly useful when dealing with a large number of tests.
  2. Efficient Navigation: Testers can quickly navigate to the specific category they are interested in, saving time that would otherwise be spent scrolling through unrelated tests.
  3. Easier Maintenance: When tests are grouped by category, it’s easier to maintain and update them. If a change is made that affects a specific category of tests, you can quickly locate and update these tests as needed.
  4. Better Understanding: It provides a better understanding of what each test is supposed to validate by grouping related tests together.
  5. Enhanced Collaboration: When multiple testers are adding to the repo, having tests grouped by category can help prevent duplication of effort and make it easier to divide work among team members.

Effective test management is maintaining a balance between granularity and simplicity. Too many categories can make the system confusing and difficult to navigate, while too few can lead to disorganization and inefficiency.

Alternatives considered

No response

Environment Information

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the Test Explorer implementation and the Visual Studio 2022 grouping options shown in the issue, then define the supported grouping categories and how they should appear in VS Code. Done means the requested grouping behavior is specified, implemented, and verified in Test Explorer.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, vscode
Domain
testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.