Enable Java assertions in framework integration tests #539
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.
Description
This PR adds the
-ea
command line forjava
invocation when an integration test is run. The test runner code is refactored: a list of additional arguments is added, and list builders are used instead of list concatenation during the command line construction.As list builders are experimental in Kotlin 1.4.20, necessary
@OptIn
annotations and the corresponding compiler argument have been added. They will become obsolete upon transition to Kotlin 1.7.Fixes #538
Type of Change
How Has This Been Tested?
Automated Testing
A new test with
assert
statement was added to theutbot-framework
test suite:org.utbot.examples.codegen.JavaAssertTest
.Manual Scenario
It is an infrastructural change, so no explicit manual checking is expected. To verify that the change works, it is necessary to add a test involving Java
assert
statement to theutbot-framework
test suite.Checklist (remove irrelevant options):