Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Minimize UtExecution number produced by fuzzing and collect coverage statistics#465

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
Markoutte merged 2 commits intomainfrompelevin/trie
Jul 11, 2022

Conversation

@Markoutte
Copy link
Collaborator

@MarkoutteMarkoutte commentedJul 8, 2022
edited by sergeypospelov
Loading

Description

The coverage statistic should be collected to improve fuzzing. To store the result of concrete execution atrie is used. For every coverage trace the total number of the same traces available to further analysis. Also, fuzzing now doesn't generate UtExecution with same coverage trace which increases a performance a bit, because fuzzing can generate a zillion combinations.

Type of Change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Automated Testing

org.utbot.framework.plugin.api.TrieTest

Checklist (remove irrelevant options):

  • 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
  • All tests pass locally with my changes

Copy link
Member

@sergeypospelovsergeypospelov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I suggest to add some comments to public API ofTrie class, because for me some return values (e.g., fromremove andget) are not obvious.

Also, I expect (maybe wrongly), that remove from theTrie removes only one entry of the same string, but the following test fails:

    @TestfuntestSearchingAfterDeletion() {val trie= stringTrieOf("abc","abc","abcde")        assertEquals(3, trie.toList().size)val removed1= trie.remove("abc")        assertNotNull(removed1)val find= trie.get("abc")        assertNotNull(find)val removed2= trie.remove("abc")        assertNotNull(removed2)    }

@MarkoutteMarkoutte merged commitc1d1ca7 intomainJul 11, 2022
@MarkoutteMarkoutte deleted the pelevin/trie branchJuly 11, 2022 10:53
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@sergeypospelovsergeypospelovsergeypospelov approved these changes

Assignees

No one assigned

Labels

None yet

Projects

Archived in project

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Markoutte@sergeypospelov

[8]ページ先頭

©2009-2025 Movatter.jp