Thanks Jens.
Wars are so old school. Fat jars are the thing these days :).
In the integration test, I'm already creating an in-memory instance of the db which is injected into the server resources, so that part is covered.
The only question now is how to setup GWT for doing browser based integration testing. Will keep you guys posted on how it goes.
On Sun, Apr 10, 2016 at 4:40 AM, Jens <jens.nehlmeier@gmail.com> wrote:
--How can that be done? Can anyone point me to which code class / method needs to be called for starting up SDM?CodeServer.main()Also, if there's a better way of doing what I'm trying to do, or if anyone has done this before, please share your thoughts.IMHO you would usually use a build system to produce a *.war file configured for integration testing (e.g. using a specific database for integration testing), to deploy it and then start integration tests using selenium/webdriver.-- J.
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/oZvdPi9T844/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@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.
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+unsubscribe@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.
No comments:
Post a Comment