On Thursday, August 4, 2016 at 9:26:27 PM UTC+2, Kay Pac wrote: > > 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. >
GWTTestCase is there to test code that needs to run in a "GWT/browser" context: widgets, elements, events, super-source, etc. The <servlet> is used by GWT itself in test FormPanel, RequestBuilder and GWT-RPC, at the "protocol" level (i.e. with servlets designed to trigger specific code paths in client-side code –and server-side code for GWT-RPC– depending on the request). > 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. > The gwt-maven-plugin⋅s are independent projects. Mojo's Maven Plugin for GWT categorizes GWTTestCase as integration tests (historically, I believe) mainly because they're slow and involve many moving pieces: they're undoubtedly "bigger" than "unit" tests. I, for one, treat them more as unit tests, and my Maven Plugin for GWT (net.ltgt.gwt.maven:gwt-maven-plugin) runs them at the "test" phase. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
