Clarify scope of EXPLICITLY_THROWN_UNCHECKED_EXCEPTIONS test suite

[alisevych]

Description

Clarify scope of generated suite with EXPLICITLY_THROWN_UNCHECKED_EXCEPTIONS.

Expected behavior

Is it correct that only explicitly thrown exceptions without try-catch should be located in this suite?

Environment

Fuzzing is on.

Context

Example:

Test with String.repeat(-1) throws [java.lang.IllegalArgumentException: count is negative: -1]

Expected result

The test should be put into FUZZING: IMPLICITLY_THROWN_UNCHECKED_EXCEPTIONS region.

Actual result

The test is currently put into FUZZING: EXPLICITLY_THROWN_UNCHECKED_EXCEPTIONS region.

Originally posted by @alisevych in #1102 (comment)

[amandelpie]

I am happy to discuss about clusters for fuzzing tests bazed on the utExecution.result.

At this moment all unsuccessful fuzzing execution are grouped to the one cluster with the name "EXPLICITLY_THROWN_UNCHECKED_EXCEPTIONS", probably the common name is incorrect

Also, I could create a separate clusters for all types of utExecution.result

• UtConcreteExecutionFailure
• UtExplicitlyThrownException
• UtImplicitlyThrownException
• UtOverflowFailure
• UtSandboxFailure
• UtTimeoutException
  But @Markoutte looks like not all results are possible for Fuzzing execution, am I right?

[Markoutte]

If it collects exceptions of any kind, I'd prefer name like "EXCEPTIONS_THROWN" without any details about checked/unchecked.

[korifey]

If it collects exceptions of any kind, I'd prefer name like "EXCEPTIONS_THROWN" without any details about checked/unchecked.

We should at least differentiate Error suite from regression suite

[alisevych]

As a suggestion:
EXPECTED_EXCEPTIONS
UNEXPECTED_EXCEPTIONS