Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SettingsMigrator: Remote execution is not added in .runsettings
See original GitHub issueDescription
I used SettingsMigrator.exe tool for convert .testsettings to . runsettings. Remote execution parameters has been skipped in .runsettings file
Expected behavior
Add remote execution settings in converted .runsettings file
Actual behavior
TestSettings:
<RemoteController name="Testcontroller" />
<Execution location="Remote" parallelTestCount="2">
Converted .runsettings file
<MSTest>
<ForcedLegacyMode>true</ForcedLegacyMode>
</MSTest>
<LegacySettings>
<Execution parallelTestCount="2">
Is any ability to execute automated tests on remote Test controllers with .runsettings file?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@AndrewASel , the recommended way to distribute test is to use the multi agent settings in the pipeline itself. Please read https://aka.ms/testingwithphases for more info.
@AndrewASel Testing on hosted agents is supported. It has chorme and firefox browsers installed. Coded UI is not supported on hosted agents but you can run UI tests with selenium and that is the recommended approach as well. Or you can set your own agents and install anything you want. There will not be one single combined trx, but you will have one single consolidated test reporting on the server. Sure, please try this out and get back in case of questions.