You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue aims to document the reasons for why debugging does no longer work and does not expect a fix soon
Since v0.8.0 or more precisely since #201, debugging using the graderPublicRun or graderPrivateRun tasks is no longer possible.
why?
In order to address #83 and some other issues such as memory leaks and only partial Mockito-Support, jagr decided to replace the gradle-specific executor mode with the process-mode which downloads the fat-jar and uses this to run all the tests. While this archieves the goal of fully supporting mockito (and especially mockStatic), it renders the gradle debugger useless for now.
how to fix?
In order to fix this issue, a whole new execution mode using java-exec would be necessary, which is currently not planned.
what to do instead?
Since popular mocking frameworks are now fully supported, the test-creators can and should ensure regular Junit-compatibility as much as possible which will enable granular per-test debugging and should now work mostly the same within jagr. If tests are only compatible with full jagr runs, they should be marked as such.
TL;DR
Test development is now easier than ever, but debugging should be done in Junit for now.
The text was updated successfully, but these errors were encountered:
Since v0.8.0 or more precisely since #201, debugging using the
graderPublicRun
orgraderPrivateRun
tasks is no longer possible.why?
In order to address #83 and some other issues such as memory leaks and only partial Mockito-Support, jagr decided to replace the gradle-specific executor mode with the process-mode which downloads the fat-jar and uses this to run all the tests. While this archieves the goal of fully supporting mockito (and especially mockStatic), it renders the gradle debugger useless for now.
how to fix?
In order to fix this issue, a whole new execution mode using java-exec would be necessary, which is currently not planned.
what to do instead?
Since popular mocking frameworks are now fully supported, the test-creators can and should ensure regular Junit-compatibility as much as possible which will enable granular per-test debugging and should now work mostly the same within jagr. If tests are only compatible with full jagr runs, they should be marked as such.
TL;DR
Test development is now easier than ever, but debugging should be done in Junit for now.
The text was updated successfully, but these errors were encountered: