Closed ndrwdn closed 7 years ago
Thanks for the pull request. I am going to look over it in the following days and give you some feedback.
I think it's OK not to write tests for this. It sounds fairly complex to me. Can we instead write some unit tests that demonstrates that the correct value is passed on to InstrumentCodeAction
?
@bmuschko Can we please get this merged in? it's causing me problems currently and i'm going to have to work off of this branch until it's merged into trunk
The contents of this PR were merged with PR#84. I added integration tests for this and updated the release notes.
This adds a parameter to the compiler options to invoke javac with the debug flag. This is to fix issues my team is having with Clover and Spring MVC code.
I would like to write a test for this, but I'm struggling with it and am hoping for some guidance. My plan for testing this is to add an integration test that invokes the plugin with the debug flag set to true and then assert using ASM to read the bytecode and verify that debugging info is present. The part I'm having trouble with is that the plugin restores the original classes, which means that after the plugin has completed running I don't have access to the instrumented classes in my test. Is there some way to turn off the restore for a test? Or perhaps, capture the instrumented classes before the restore occurs?