-
Notifications
You must be signed in to change notification settings - Fork 47
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
Regions names for parameterized tests #1301
Comments
@korifey @amandelpie @EgorkaKulikov |
@alisevych could we say now that we are satisfied for today with the existing master? |
As for regions for parameterized tests - they are readable: ///region Test suites for executable org.utbot.examples.algorithms.Sort.quickSort
///region Parameterized test for method quickSort(long[], int, int)
///endregion
///region FUZZER: Tests for method quickSort(long[], int, int)
///endregion
///endregion Can we also leave information that these tests cannot be presented as parameterized - as it was done before? |
Description
Some tests generated for ArraysQuickSort.sort in Parameterized mode are presented as regular tests.
They are put in to region
///region Tests for method sort(int[], int, int, int[], int, int) that cannot be presented as parameterized
Now there are 2 types of such tests:
To Reproduce
ArrayQuickSort
with JUnit5 and Parameterized on.Expected behavior
Regions in the generated tests are supposed to be similar to the ones generated with parameterization off.
Actual behavior
///region Tests for method sort(int[], int, int, int[], int, int) that cannot be presented as parameterized
Regions in generated tests, that cannot be presented as parameterized, do not contain information about which suite they belong to.
Fuzzing / Symbolic, Successful / Explicitly thrown exceptions / ...
Visual proofs (screenshots, logs, images)
Regions for parameterized tests:

Regions for regular tests:

Environment
IntelliJ IDEA
The text was updated successfully, but these errors were encountered: