Skip to content

Unified error and exception clusters for all UtExecutions #1250

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

Merged
merged 6 commits into from
Nov 8, 2022

Conversation

amandelpie
Copy link
Collaborator

@amandelpie amandelpie commented Oct 27, 2022

Description

We first step to solve this ticket is the unification of all error/exception clusters by result. Currently, Fuzzed and Symbolic executions are clustered in the different ways.

The main idea of this PR is the following:

  • use the same cluster descriptions for both, Fuzzed and Symbolic executions
  • fix some JavaDocs
  • remove outdated successful/unsuccessful cluster descriptions
  • some parts of common logic for grouping failed executions were extracted to the common method addClustersOfFailedExecutions

Fixes #1133

Type of Change

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

@amandelpie amandelpie force-pushed the amandelpie/feature-1133 branch from 4e3d8a0 to b60564c Compare October 31, 2022 12:00
@amandelpie amandelpie marked this pull request as ready for review November 2, 2022 08:27
@amandelpie amandelpie requested a review from Markoutte November 2, 2022 08:30
@amandelpie amandelpie merged commit 304b3ba into main Nov 8, 2022
@amandelpie amandelpie deleted the amandelpie/feature-1133 branch November 8, 2022 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify scope of EXPLICITLY_THROWN_UNCHECKED_EXCEPTIONS test suite
2 participants