Skip to content
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.

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

Open up traits for consumption by extensions #5265

Open
Evangelink opened this issue Mar 19, 2025 · 0 comments
Open

Open up traits for consumption by extensions #5265

Evangelink opened this issue Mar 19, 2025 · 0 comments
Assignees
Labels
Area: MTP Extensions Area: MTP VSTest Bridge Area: MTP Belongs to the Microsoft.Testing.Platform core library

Comments

@Evangelink
Copy link
Member

As of now, when using traits with MTP you have 2 options:

  • MetadataProperty - used by TUnit, xUnit v3, TATF
  • the internal serializable kvp property - used by the bridge

When an extension wants to act on this property it currently can do it only on MetadataProperty which won't work for VSTest bridge extensions (MSTest, NUnit...). The bridge should be changed to no longer use the serializable property but instead rely on the MetadataProperty.

Ideally, in order to reduce memory consumption, these properties should not always be emitted by the test framework and we should have a capability like we have for TRX that would allow clients or extensions to declare they are interested about such properties so that test framework can conditionally emit them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: MTP Extensions Area: MTP VSTest Bridge Area: MTP Belongs to the Microsoft.Testing.Platform core library
Projects
None yet
Development

No branches or pull requests

3 participants