To add to Peter's comment, the JUnit/GWTTestCase coverage is still valuable, despite Selenium, because it allows fast identification of errors at an easily identifiable granularity.
For example, on a current GWT project with 1K classes, if a UI automation test failed with Selenium, then we know there is a problem, but it could be at many layers of our stack. Further, running our 2K Selenium (we use Cucumber, but very similar) tests takes two hours. Our developers are not going to run this before they checkin. But, our 3K JUnit/GWTTestCase tests take only 8 minutes to run. This way we can use features like TeamCity's *Pretested Commit* and run these tests before allowing a commit, and if a failure happens, it's been isolated to the class and method level for quick fixing. Also note, you can easily test the RPC calls from GWTTestCase, see Asyncronous GWTTestCase<https://developers.google.com/web-toolkit/doc/latest/DevGuideTesting#DevGuideAsynchronousTesting> . Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/qLoEyyiSLHkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
