On Sunday, May 1, 2016 at 5:46:26 PM UTC+2, Jens wrote: > > Depending on what exactly you want to test I would try hard using plain > JUnit with mocking / stubbing. Testing @JsType(native = true) annotated > interfaces / classes probably does not make a lot of sense given that the > underlying JS code should already be tested and given that GWT itself has > tests to ensure that JsInterop works correctly. > > But in general GWTTestCase should just work with JsInterop because they > should be executed in web-mode by default now. >
I think you *have* to run them in prod mode though (this is now the default, but in case your gwt.args contains an explicit -devMode, you may want to remove it or replace it with -web or -prod) -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/73974bec-3e59-4b92-8553-004b29069624%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
