Repository navigation
Access to Filer, assert about generated files #58
Description
Activity
I ended up writing my own based on
JavacPathFileManagerand Jimfs. Do with this as you please.Yes, that's totally the right way to go. If you are just testing the filer, make a fake filer - getting the one from
CompilationRuleis a little weird anyway since that's all part of a fake compilation that actually encloses the test. If you're on 1.7+,JavacPathFileManagerand Jimfs are definitely preferred to my semi-hacky implementation.Hi @JakeWharton and @gk5885 ,
do you have a working example of this ? I don't only want to compile the generated code, I would also like to execute it (load it into memory, even if by reflection).
Follows up #70
Access to the
Fileris trivial to add toCompilationRule. What I can't figure out is how to propagate the generated content back to the test to assert on the generated sources. At the very least it would require a change toCompilationto inject theInMemoryJavaFileManagerso it could also be made available to the test but that brings other dependencies with it. PerhapsCompilationshould be more stateful than just static helpers?I'm not doing any actual compilation. I want to only test interactions with a
Filerand assert on its outputs.Happy to implement, just want guidance/approval on the approach.