René's URL Explorer Experiment

Title: Make UtEnumConstModel and UtClassRefModel reference models #414 by dtim · Pull Request #611 · UnitTestBot/UTBotJava · GitHub

Open Graph Title: Make UtEnumConstModel and UtClassRefModel reference models #414 by dtim · Pull Request #611 · UnitTestBot/UTBotJava

X Title: Make UtEnumConstModel and UtClassRefModel reference models #414 by dtim · Pull Request #611 · UnitTestBot/UTBotJava

Description: Description Historically UtEnumConstModel and UtClassRefModel have been processed not as other reference models, but in a special way, more like to primitive types. This approach leads to several problems, especially to class cast errors when processing generic collections with enums or class references as elements. This commit makes UtEnumConstModel and UtClassRefModel subtypes of UtReferenceModel. Concrete executor is modified to respect the identity of static fields to avoid rewriting enum values and Class instances. Special processing for enums is implemented. When a new enum value is created, or an Object is being cast to the enum type, static values for the enum class are initialized, and the set of hard constraint is added to require that the new instance has the same address and ordinal as any one of enum constants to implement reference equality for enums. Corresponding changes in fuzzer model providers have been implemented. Limitations (probably have been there for a long time, addressed separately): anonymous nested classes associated with enum values are not fully supported yet: #617 (maybe a codegen limitation); enum constants are explicitly assigned to corresponding static fields in generated tests: #618 (it seems to be a particular case of our general approach to static field initialization); instances of enum classes are (unsuccessfully) generated via reflection by the concrete executor: #619. Fixes #414 (meta-issue) Fixes #230 Fixes #300 Type of Change Breaking change (fix or feature that would cause existing functionality to not work as expected) How Has This Been Tested? Automated Testing All existing unit tests should pass. New unit tests for enums have been added: org.utbot.examples.enums.ComplexEnumExamplesTest Note: the test org.utbot.examples.enums.ComplexEnumExamplesTest#testFindState is currently disabled because of limited anonymous classes support. Manual Scenario To check that #230 is fixed: generate the test suite for the code example in issue #230 description. Test should be generated, no exceptions should be thrown. To check that #300 is fixed: run the contest estimator with settings from issue #300 description. Generated file should compile, class name should be present in qualified enum constant names. Checklist: This is the author self-check list The change followed the style guidelines of the UTBot project Self-review of the code is passed The change contains enough commentaries, particularly in hard-to-understand areas New documentation is provided or existed one is altered No new warnings New tests have been added All tests pass locally with my changes

Open Graph Description: Description Historically UtEnumConstModel and UtClassRefModel have been processed not as other reference models, but in a special way, more like to primitive types. This approach leads to several p...

X Description: Description Historically UtEnumConstModel and UtClassRefModel have been processed not as other reference models, but in a special way, more like to primitive types. This approach leads to several p...

Opengraph URL: https://github.com/UnitTestBot/UTBotJava/pull/611

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width