Add tests on the build, trimmed, self-contained command-line binaries #456
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.Net gets more and more trimming and compiling features going forward, and, if we e.g. should replace System.Commandline, which never seems to get out of beta, with another command-line parsing library, I feel much more confident doing this if we have a lot of tests on the packaged an build binaries too, in addition to the DLLs directly. I reused the existing unit tests, being a bit creative with the .csproj files and includes. I _hope_ it is a good idea, and that we don't have to duplicate up any new tests we should write on the migrations for both DLLs/libraries and command-line. Including the files should make the tests be available for both automagically. * Add test projects for all databases for compiled command-line grate executable * Add running of these tests to the Build and Release build pipeline * Extracted unit test project imports to separate .targets file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.Net gets more and more trimming and compiling features going forward, and, if we e.g. should replace System.Commandline, which never seems to get out of beta, with another command-line parsing library, I feel much more confident doing this if we have a lot of tests on the packaged an build binaries too, in addition to the DLLs directly.
I reused the existing unit tests, being a bit creative with the .csproj files and includes. I hope it is a good idea, and that we don't have to duplicate up any new tests we should write on the migrations for both DLLs/libraries and command-line. Including the files should make the tests be available for both automagically.