Test explorer doesn't show suite correctly
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- testing-qa
Research direction
Reproduce the issue using the provided .NET Standard project steps, with the Jest or Jasmine examples from the report, and inspect how Visual Studio Test Explorer parses file::suite::test names. Done means the explorer preserves the Project > File > Suite > Test hierarchy, including dotted filenames, suite names, and top-level tests.
Written by the indexing model from the issue text.
Description
Expected Behavior
Javascript tests are displayed in VS Test Explorer by Project > File > Suite > Test
Actual Behavior
The tests output shows the details of file::suite::test
Creating Test Case:tests\FormatServiceTests.js::FormatService - format()::date
Creating Test Case:tests\XAxisTests.js::global::XAxisService.axis() - Index Values
But the test explorer seems to split on the last . and shows js instead of FormatService - format()
and XAxisService > axis() - Index Values instead of global > XAxisService.axis() - Index Values


These examples are in Jest (26.4.2), but I've seen the same issue trying Jasmine.
FormatServiceTests is using
describe("FormatService - format()", () => {
test("date", () => {
...
});
});
while
XAxisTests is a top level test
test("XAxisService.axis() - Index Values", () => {
...
});
- NTVS Version: 1.5.20902.1 Commit Hash:b474efcb6f92db52a8f8e2e6a8cb9648476885cc
- Visual Studio Version: 16.8.0 Preview 3.2
- Node.js Version: 10.15.0
Steps to reproduce
- Create a .netstandard project following https://docs.microsoft.com/en-us/visualstudio/javascript/unit-testing-javascript-with-visual-studio?view=vs-2019#unit-test-net-core-and-net-standard
- Add test files into the
testsfolder and rebuild the project
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/nodejstools
-
microsoft/nodejstools#2523 · 1 reaction · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/nodejstools#2519 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoft/nodejstools#2517 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
microsoft/nodejstools#2514 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/nodejstools#2513 · 5 comments ·
All issues in microsoft/nodejstools
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·