formulahendry / formulahendry/vscode-dotnet-test-explorer

Grouping of MSTest DataRow DataTestMethods.

Open
#354 1 comment 3 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
208
Forks
93
PR merge metrics
No merged PRs in 30d

Description

Currently, an MSTest project using DataTestMethods will start out looking like the following. Note that the DataTestMethod is listed twice.
![ExampleInitial](https://user-images.githubusercontent.com/97324847/155637686-49b5ffa7-9f61-4941-9d0d-4af5ffb46abe.PNG)

But after running the tests, more lines are added for each DataRow, but note that the first two lines are still the duplication of the DataTestMethod name. Additionally, it seems that one or both of those lines should be updated with a red "X" instead of the grey "?".
![ExampleWithFailures](https://user-images.githubusercontent.com/97324847/155637941-e624f1e9-35e6-460d-9331-d9389c6f4127.PNG)

Additionally, note that even if all of the DataTestMethod's DataRows pass, the first two lines are still the duplicate DataTestMethod name. Additionally, note that we still see a grey "?" instead of the expected green "✓".
![ExampleGood](https://user-images.githubusercontent.com/97324847/155638666-59169fa7-271e-4817-b8fb-74092257aecb.PNG)

Lastly, a feature request would be that the DataTestMethod is treated as a group which can be expanded to list all the DataRows below it.

I am running .NET 17.0.0, VS Code 1.64.2, MSTest Test Adapter / Framework 2.2.8, .NET Core Test Explorer 0.7.7, and Linux Ubuntu 20.04.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue in VS Code with an MSTest DataTestMethod containing DataRows, using the screenshots and reported environment as the expected context. Trace the test explorer's result grouping and status display, then verify that duplicate method entries are removed, statuses reflect the DataRows, and the method can expand to show them.

Written by the indexing model from the issue text.

Assessment

Domain
devtools, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.