I'm attempting to figure out the best way to setup integrated testing in
GWT. I've recently played with Rails where its really easy to launch the
application and click on buttons / fill in fields, etc to simulate user
behavior, and ensure the app works as expected. I'm looking for a similar
sol
> 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
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
integra
Once CodeServer.main() has been run, is there a way to stop the code
server, such as in the tear down method of the test?
On Sun, Apr 10, 2016 at 4:40 AM, Jens wrote:
>
> How can that be done? Can anyone point me to which code class / method
>> needs to be called for starting up SDM?
>>
>
> Code
> Once CodeServer.main() has been run, is there a way to stop the code
> server, such as in the tear down method of the test?
>
Hmm no. I guess you would need to run it as a separate process and then
kill the process. But always starting/killing SDM also costs you time so
personally I would
You could setup a stop key for the jetty and stop this with this key later.
--
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...@googlegr