Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Summaries for tests generated by fuzzer are generated not in the summary module #597

Closed
amandelpie opened this issue Jul 27, 2022 · 0 comments · Fixed by #599
Closed

Summaries for tests generated by fuzzer are generated not in the summary module #597

amandelpie opened this issue Jul 27, 2022 · 0 comments · Fixed by #599
Assignees
@amandelpie
Labels
comp-fuzzing Issue is related to the fuzzing comp-summaries Something related to the method names, code comments and display names generation ctg-refactoring Issue related to refactoring process

Comments

@amandelpie
Copy link
Collaborator

amandelpie commented Jul 27, 2022 •
edited
Loading

Description

The main purpose of this issue is just refactoring without behavior changes

Now, the NameSuggester API in fuzzing module is responsible for the name/display name generation.
At this moment we could differ tests generated by fuzzer and by symbolic execution according #581 and as a result could share the same approaches to name methods, generate comments and display names.

Expected behavior

After moving names/display names generation for tests generated by fuzzer to the summary module we will have the unite stage for test/names/generations.

Also it could lead to the benefits with special custom tags in JavaDocs for tests generated by fuzzer only.

NOTE: need to add some tests for generated names/display names
@korifey korifey moved this to Todo in UTBot Java Jul 27, 2022
@amandelpie amandelpie self-assigned this Jul 27, 2022
@amandelpie amandelpie added ctg-refactoring Issue related to refactoring process comp-summaries Something related to the method names, code comments and display names generation comp-fuzzing Issue is related to the fuzzing labels Jul 27, 2022
This was referenced Jul 27, 2022
Merged
Closed
amandelpie added a commit that referenced this issue Aug 8, 2022
@amandelpie
Summaries for tests generated by fuzzer are generated in the summary …
5339ce1 
…module #597 (#599)

* Just moved some classes and shifted the stage of name generation for fuzzing tests

* Made some refactoring

* Fixed a bug

* Changed signatures

* Fixed merge issues

* Add some fixes

* Add some fixes

* Add some fixes

* Fixed some places

* Fixed some places

* Fixed some places

* Fixed wildcard imports
Repository owner moved this from Todo to Done in UTBot Java Aug 8, 2022
denis-fokin pushed a commit that referenced this issue Aug 18, 2022
@amandelpie @denis-fokin
Summaries for tests generated by fuzzer are generated in the summary …
9fb393f 
…module #597 (#599)

* Just moved some classes and shifted the stage of name generation for fuzzing tests

* Made some refactoring

* Fixed a bug

* Changed signatures

* Fixed merge issues

* Add some fixes

* Add some fixes

* Add some fixes

* Fixed some places

* Fixed some places

* Fixed some places

* Fixed wildcard imports
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amandelpie amandelpie

Labels
comp-fuzzing Issue is related to the fuzzing comp-summaries Something related to the method names, code comments and display names generation ctg-refactoring Issue related to refactoring process
Projects
UTBot Java
Archived in project
Milestone
No milestone
1 participant
@amandelpie