[Bug]: Playwright MSTest.Sdk Uses MSTest Runner, Ignoring runsettings Configuration / Microsoft.Testing.Platform

Version

1.50.0

Steps to reproduce

When using Playwright version 1.50.0 with MSTest.Sdk version 3.8.1, the MSTest runner is used instead of the expected VSTest runner. As a result, the Playwright configuration section in the runsettings file is ignored. Key settings such as BrowserName, ExpectedTimeout, Headless, and Channel do not work.

However, when <UseVSTest>true</UseVSTest> is explicitly set in the .csproj file, and the VSTest runner is used, the Playwright settings in the runsettings file work as expected.

Expected behavior

• Playwright should respect the runsettings file when running tests with MSTest.Sdk.
• Playwright-specific settings such as BrowserName, ExpectedTimeout, Headless, and Channel should be applied correctly, regardless of whether MSTest or VSTest is used.

Actual behavior

• With MSTest runner, the Playwright settings in runsettings are ignored.
• With VSTest runner (<UseVSTest>true</UseVSTest>), the settings work as expected.

Additional context

This issue suggests that MSTest.Sdk is defaulting to the MSTest runner instead of the VSTest runner, which does not properly load the Playwright settings from runsettings. It would be helpful if Playwright could support runsettings consistently across different test runners.

Would appreciate any insights or fixes on this issue. Thanks!

Environment

- Playwright Version: 1.50.0
- MSTest.Sdk Version: 3.8.1
- .NET Version: net8.0

Reproduce the issue with Playwright 1.50.0, MSTest.Sdk 3.8.1, and net8.0 using the .csproj and runsettings configuration described. Compare behavior with and without true, then trace how Playwright-specific settings are loaded under each runner. Done means BrowserName, ExpectedTimeout, Headless, and Channel are applied consistently with MSTest and VSTest.