-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Make Tests Great Again #3231
Make Tests Great Again #3231
Conversation
… with ConfigurationBuilder)
@@ -43,14 +50,16 @@ | |||
<ItemGroup> | |||
<PackageReference Include="DiffLib" /> | |||
<PackageReference Include="CliWrap" /> | |||
<PackageReference Include="Microsoft.Extensions.Configuration" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two new nuget deps for reading a JSON file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, for reading it like a proper settings file. The intent was to be able to later extend it if necessary.
/// "TestsAssemblyTempPath": "d:\\test\\" | ||
/// } | ||
/// </summary> | ||
internal static class TestsAssemblyOutput |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not simply make this part of the Tester class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not really partial about the location, it kind of felt like easier not polluting Tester with another concern that is config-driven.
There are still specialized runners (RoundtripAssembly) or CompileCSharp with null outputfile parameter that will dump assemblies in other places.