Skip to content
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.

Improve classNowCheckedException accuracy #51

Open
lmove opened this issue Oct 3, 2019 · 0 comments
Open

Improve classNowCheckedException accuracy #51

lmove opened this issue Oct 3, 2019 · 0 comments
Labels
question Further information is requested

Comments

@lmove
Copy link
Contributor

lmove commented Oct 3, 2019

To detect the classNowCheckedException we have the following specification:

  • Consider concrete subtypes of the modified class affected by the change.
  • Report on client methods.
  • An affected method throws and creates an instance of the now checked exception.
  • An affected method does not include the exception in the throws declaration.

With M3 we only have access to information related to the exception initialization. Information related to checked and thrown exceptions is missing, even though it is available in the bytecode. We need to check alternatives to correctly report this issue. Some options are using flybytes and adding the exceptions relation to `M3'.

Without this solution we can have an approximation where we report on client methods that call the constructors of the now checked exception.

@lmove lmove added the question Further information is requested label Oct 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant