Specifically, AppDomain and shadow copy. Both ReSharper and xunit have settings for these, but how should they be merged?
I can tell when xunit's values are specified or not, so can easily tell when ReSharper should provide the value, but don't know what to do when both are specified.
Currently, ReSharper takes precedence.
Reasons for:
You're using ReSharper's runner - you want to configure it, you know where to go.
Against:
The ReSharper runner should behave the same as any other runner - if the external config files are there, they should be used to get the same behaviour (although the converse isn't true - another runner wouldn't behave the same as the ReSharper runner as it doesn't have access to the ReSharper config)
Default: xUnit runner settings is used. This will allow consistent results of the tests as it's executed exactly like how it's done when running on CI server. The usefulness of unit tests are best when using with CI server, majority of which are executed using xUnit console runner.
Override: add the ability in Resharper options to allow xUnit plugin to override settings set in runner configurations with those in ReSharper unit test settings in case developer really need to.
Specifically, AppDomain and shadow copy. Both ReSharper and xunit have settings for these, but how should they be merged?
I can tell when xunit's values are specified or not, so can easily tell when ReSharper should provide the value, but don't know what to do when both are specified.
Currently, ReSharper takes precedence.
Reasons for:
Against: