Using JUnit 4 for EvoSuit #409
Open
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
Hello-zoka
requested review from
Vladislav0Art,
arksap2002 and
pderakhshanfar
and removed request for
Vladislav0Art and
arksap2002
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.
Description of changes made
I've provided information about the type of generation tools used in the TestCasePanel to be able to choose the JUnit version, not depending on LLM settings.
Closes #408
Notes
Probably there is a more accurate way to restrict the junit version, i.e., specify it in TestCase class when it's created. But in my opinion, it's strange, that the test case panel does not know anything about the method we've generated tests, while it can have different settings options affecting compilation and running tests.