8000 Test Explorer for xunit vs xunit.v3 · Issue #2040 · microsoft/vscode-dotnettools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Test Explorer for xunit vs xunit.v3 #2040

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
segeda opened this issue May 23, 2025 · 2 comments
Open

Test Explorer for xunit vs xunit.v3 #2040

segeda opened this issue May 23, 2025 · 2 comments
Assignees
@ocallesp
Labels
area-test Test discovery, execution, debugging bug Something isn't working

Comments

@segeda
Copy link
segeda commented May 23, 2025

Type: Bug

  1. I create clean solution.
  2. Add project with xunit tests.
  3. Add project with xunit.v3 tests.
  4. In terminal run dotnet restore, dotnet build, dotnet test

All tests pass.

But in Test Explorer are only tests from xunit project.
Only tests in xunit test project have play button in gutter.

Tests from xunit.v3 project are not shown.

Extension version: 1.19.63
VS Code version: Code 1.100.2 (848b80aeb52026648a8ff9f7c45a9b0a80641e2e, 2025-05-14T21:47:40.416Z)
OS version: Darwin arm64 24.5.0
Modes:

System Info
Item Value
CPUs Apple M3 Pro (11 x 2400)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 1, 2, 2
Memory (System) 18.00GB (0.31GB free)
Process Argv --crash-reporter-id 96e5a3e1-05b3-430c-a8d3-980593299045
Screen Reader no
VM 0%
A/B Experiments 
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
a9j8j154:30646983
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
pythonrstrctxt:31112756
nativeloc1:31192215
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31313793
996jf627:31283433
pythonrdcb7:31303018
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
pylancecolor:31314202
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
gendocf:31295004
@github-actions github-actions bot added the area-test Test discovery, execution, debugging label May 23, 2025
@webreidi webreidi added the bug Something isn't working label May 27, 2025
@ocallesp
Copy link
Member
ocallesp commented May 28, 2025 •
edited
Loading

@segeda,

Thank you for reporting this issue. I have a couple of questions that might help us resolve the problem:

  1. Are you using xnit.v3 version 2.0.2?
  2. Have you tried the solutions mentioned in this https://code.visualstudio.com/docs/csharp/cs-dev-kit-faq#_why-are-my-tests-not-being-discovered-or-run-in-the-test-explorer?

Looking forward to your response so we can do further investigation

@segeda
Copy link
Author
segeda commented May 29, 2025

Thanks you @ocallesp

  1. I have version 2.0.2
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.13.0" />
    <PackageReference Include="xunit.v3" Version="2.0.2" />
    <PackageReference Include="xunit.runner.visualstudio" Version="3.1.0" />
  1. I tried it, but doesn't change anything.
  2. I also tried add
    <TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>
    <UseMicrosoftTestingPlatformRunner>true</UseMicrosoftTestingPlatformRunner>

but without success

@ocallesp ocallesp self-assigned this May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ocallesp ocallesp

Labels
area-test Test discovery, execution, debugging bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@segeda @ocallesp @webreidi
0