Improve test coverage#137
Merged
Merged
Conversation
|
This file contains hidden or 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
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.



Summary
Improve test coverage across the staging APIs, decision engine, data providers, and algorithm-specific data wrappers. Add enforceable coverage thresholds and separate the slow CS comparison suite from regular builds.
Changes
Expanded test coverage
Staging.getInputsandgetOutputsAPIs:SchemaLookuptests:DecisionEnginebranch scenarios:Coverage enforcement
verify:Current coverage:
CS comparison separation
src/cs-comparison/javasrc/cs-comparison/resourcesCsComparisonRunner.cs-comparisonMaven profile.build-helper-maven-plugin3.6.1exec-maven-plugin3.6.3Regular builds no longer compile the comparison runner or copy its 115 large resource files.