I am currently using gwt 2.3 and smartgwtpower 2.5 nightly and using
Eclipse on Linux. My web app is using common code, developed in house,
and packaged to a jar called commonsmartgwt.jar. In this jar is the
entry point class and has its own gwt.xml file. In my web app's
gwt.xml file I inherit
Hi Ignat,
I definitely agree with you and follow this model. Not everyone does
and in some cases you're stuck unit testing your views. If you're
able, definitely one should follow what you said.
All the best,
--
Arthur Kalmenson
On Wed, Nov 3, 2010 at 8:51 AM, Ignat Alexeyenko
Arthur,
These rules are just good OO design - when you are depend on interfaces
rather than concrete classes.
One of the pros of following this principles - you can simplify testing by
using mocks instead of real objects.
You can read more about why programming to interfaces are so importang.
You can still mock out GWT widgets, but you'll need to use the
GWTMockUtilities. You can find more info here:
http://onthejvm.com/mocking-your-gwt-widgets-without-gwttestcase
--
Arthur Kalmenson
On Fri, Oct 29, 2010 at 9:14 AM, chrisr chris.robert.rowl...@gmail.com wrote:
Hi Ignat, thank you
Hi!
In GWT you can write:
- plain JUnit tests,
- tests that are running inside browser (see GwtTestCase).
You can hide instance of DataPicker behind HasValue interface.
I.e. use:
HasValueDate dataPicker
instead of:
DataPicker dataPicker
This will allow you to create a mock for a dataPicker
Hi Ignat, thank you for the tip. I do remember reading that there is
a way to write gwt junit tests in a way that were much faster than the
way I'm doing it now. I wonder if this is it.
Is there some documentation for how to write unit tests of this
variety? I searched but didn't come across
I've been writing JUnit tests for my GWT code for a while, and I've
always come across issues where it feels like something very simple
doesn't work. Usually I can figure out a way to make it work, however
that usually feels wrong...
Right now I'm trying to write a test that involves an instance
