Skip to content

VSTestBridge doesn't use TestMethodIdentifierProperty #5406

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
Closed
Youssef1313 opened this issue Apr 6, 2025 · 0 comments · Fixed by #5409
Closed

VSTestBridge doesn't use TestMethodIdentifierProperty #5406

Youssef1313 opened this issue Apr 6, 2025 · 0 comments · Fixed by #5409
Assignees
@Youssef1313
Labels
Area: MTP Extensions Area: MTP VSTest Bridge Area: MTP Belongs to the Microsoft.Testing.Platform core library
Milestone
MSTest 3.9 / MTP 1.7

Comments

@Youssef1313
Copy link
Member

Youssef1313 commented Apr 6, 2025 •
edited
Loading

This property can be used by extensions to know test information.

The only thing we add in VSTestBridge is vstest.TestCase.FullyQualifiedName which is even done only for VS and isn't publicly accessible.

We need a reliable way to correctly add TestMethodIdentifierProperty, but maybe we are limited by VSTest there.

Ideally, we would get rid of VSTestBridge completely and have an MSTest implementation completely based on MTP, but NUnit is also using the bridge so it would be good if we can fix the bridge as well
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Youssef1313 Youssef1313

Labels
Area: MTP Extensions Area: MTP VSTest Bridge Area: MTP Belongs to the Microsoft.Testing.Platform core library
Projects
None yet
Milestone
MSTest 3.9 / MTP 1.7
1 participant
@Youssef1313