Sunday, September 17, 2017

Re: Test Strategies for Modern GWT (i.e. Elemental2 etc)

AFAICT Elemental 2 doesn't really have any code to be tested (Java methods directly map to JS methods). You would test the browser API itself which browser vendors already do. So I would mock any elemental 2 class and use JUNIT to test whatever component/abstraction you build on top of elemental 2. And if elemental 2 has some @JsOverlay methods then elemental 2 should already have a test for it.

What you should do anyways is end to end testing using webdriver/selenium to make sure the app experience does not change and UI behavior works as designed. IMHO these are the most important but also most time consuming tests. 

-- J.

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment