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 to export test function to the global scope (as the javascript framework expects).
There is no hybrid mode GwtTestcCase/JunitShell that tries to drive to compile or make things look like regular JVM test. End result is a pure javascript suite executed by a javascript test framework driver. On Fri, Jan 26, 2018 at 2:59 PM, Thomas Broyer <[email protected]> wrote: > 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 > to find test, setup, teardown methods/functions by naming rules) > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/google-web-toolkit-contributors/a083c6c4-43aa- > 44f0-a639-2eab1a12a2c7%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3VuGnA%3DSYePvb5JfdGWJe%3DFOXvThJGg5arJ1Fehi-nBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
