Yes, that's correct.
It is a simple system with two part generation.
First part in bazel that generates an empty java class with a class
annotation that points to JUnit suite to trigger APT.
The second part in APT that generates the wrapper around junit3/junit4
tests that are listed in the suite t
Correct me if I'm wrong, this is relying on JUnit 4 suited to generate
appropriate goog.testing code, JUnit 3 test cases (GWTTestCase basically,
possibly simply TestCase), with a "new" emulation of those classes based on
JsInterop to goog.testing, right? (goog.testing behaving similar to JUnit 3
+dramaix +dankurka
It doesn't support runners nor rules; just the basic stuff.
@dramaix: Let's release the source of J2CL junit emulator under the J2CL
repo. We don't need to wait until it works for bazel.
On Fri, Jan 26, 2018 at 12:02 PM, Colin Alworth wrote:
> As we look at how to keep migra
As we look at how to keep migrating GWT provided user modules to modern
best practices, the JUnit runner is a hairy one - it relies on a lot of the
practices we discourage, including a great many modules in GWT that we
might prefer it not use. It also assumes
As has been discussed on other list