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

Should MTP support RunSettingsFilePath MSBuild property in addition to the --settings command-line option? #4636

Closed
Youssef1313 opened this issue Jan 14, 2025 · 2 comments
Labels
Area: Testing Platform Belongs to the Microsoft.Testing.Platform core library State: Won't Fix

Comments

@Youssef1313
Copy link
Member

Currently, to pass a runsettings file to MTP, you need to use --setings. With VSTest, an MSBuild property RunSettingsFilePath was supported.

Do we want to support RunSettingsFilePath MSBuild property in MTP as well?

In all cases, a doc update to the following is required:

@Youssef1313 Youssef1313 added the Area: Testing Platform Belongs to the Microsoft.Testing.Platform core library label Jan 14, 2025
@nohwnd
Copy link
Member

nohwnd commented Jan 14, 2025

This imho opens it up for having a different runsettings file per project, I would be careful with that. We have that feature in vstest and it leads to confusion which settings can and cannot be applied to the run, and it forces us to run 1 vstest.console per test project to be able to consider these runsettings.

@Evangelink
Copy link
Member

I would also vote for no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Testing Platform Belongs to the Microsoft.Testing.Platform core library State: Won't Fix
Projects
None yet
Development

No branches or pull requests

3 participants