Specify file names in generatesFiles() about compile-testing HOT 3 CLOSED

Can you clarify - you are wanting an option to specify what files are generated, or what files are expected to be generated? Can you write a bit of example test code that you would expect would invoke the behaviour you want, please?

from compile-testing.

I'm not sure what the distinction between are generated or are expected to
be generated is.

I've got a plugin that produces a file with some metadata for a number of
java files. ex: For each java file it produces a file with a count of all
of the subclasses.

I give it input
class Foo {
class Moo {
class Boo {
}
class Grue {
}
}
class Blue {
}
}

Now, I expect that my annotation processor will produce files
Foo.count: 2
Moo.count: 2
Boo.count: 0
Grue.count: 0
Blue.count: 0

And my test is:
assert_()
.about(javaSource())
.that(getJavaSourceFileObject("Foo.java"))
.processedWith(new SubclassCounter())
.compilesWithoutError()
.and()
.generatesFiles(
getJavaFileObject("expect/Foo.count"),
getJavaFileObject("expect/Moo.count"),
getJavaFileObject("expect/Boo.count"),
getJavaFileObject("expect/Grue.count"),
getJavaFileObject("expect/Blue.count"));

Unfortunately my plugin isn't very good and doesn't generate data for
subclasses so the output is:
Foo.count: 2
Moo.count: 2
Blue.count: 0

Yet, this will pass because it looks at the data from those expected files
(2, 2, 0, 0, 0) and finds that a matching file exists.

Hopefully that makes a bit more sense (or the failure in my logic is
clearer)

On Sun, Oct 12, 2014 at 9:41 PM, Christian Edward Gruber <
[email protected]> wrote:

Can you clarify - you are wanting an option to specify what files are
generated, or what files are expected to be generated? Can you write a
bit of example test code that you would expect would invoke the behaviour
you want, please?

—
Reply to this email directly or view it on GitHub
#54 (comment)
.

from compile-testing.

This now works with CompilationSubject

from compile-testing.