On Apr 24, 2:04 am, Paul Stockley <[email protected]> wrote: > I like the model-view-presenter architecture. However I am not at all > sold on mocking out the view and testing just the presenter. The > problems is that you are not testing 3 of the potentially most error > prone parts of the system: 1) The browser and DOM, 2) The GWT widget > library and 3) the GWT java to javascript conversion. So you still > need to test these otherwise you are fooling yourself about the > reliability of your code. I would rather discared the interfaces, unit > test my rpc services using junit and use something like webdriver to > test the front end.
One of the goal of using MVP is to unit test in "pure java", which is waaay faster than using a GWTTestCase or WebDriver. But of course it only tests the "presentation logic" (the presenter), which means you SHOULD do other tests, automated using GWTTestCase or WebDriver, or manual tests. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
