I guess I am confused. I understand the need to do as much testing as possible with regular JUnit/TestNG tests, which I try to do. What I don't understand precisely is where the area of coverage for GWTTestCase is - it's some area between vanilla JUnit and Selenium/Webdriver, but it's clear I don't understand what that area is or how to take advantage of it. I am certain the structure of my code is a problem - I hacked some bits together and embedded a dependency on a spring gwt webservice, which I can't run within the JUnitShell. It makes sense to remove that dependency and supply a mock object.
Part of my confusion, I believe, stems from the documentation for the gwt-maven-plugin, which says that it considers the GWTTestCase integration tests and not unit tests. Thus I categorize them so, and rush to try and integrate the kitchen sink. So your suggestions have helped to clear up this misunderstanding on my part, I appreciate this clarification, Thank you Thomas. On Thursday, August 4, 2016 at 4:30:43 AM UTC-7, Thomas Broyer wrote: > > JUnitShell support for <servlet> is not meant for integration tests. You > probably shouldn't try to use it that way. Either start a separate server > (using CORS), or don't use a GWTTestCase (possibly use a dedicated GWT app > and drive it through Selenium/WebDriver. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
