On Fri, Jun 15, 2012 at 7:06 AM, Mike Dee <mdichiapp...@gmail.com> wrote: > I look at MVP + JRE based testing/mocking and I have trouble seeing the > value. All of our algorithms and database interactions are pojos and we > have tons of JUnit tests written (without MVP + JRE tests/mocks). I ask > myself if there is much value in doing MVP + JRE based tests/mocks when > Selenium will exercise those same areas. Why do double the work? Maybe I > don't understand something or need to get used to the idea.
Selenium tests are slow to execute and expensive to write. MVP+mock tests are relatively fast to write and fast to execute but may not exercise the full stack. It sort of comes dow to when do you use integration tests and when do you use unit tests. So it is usually to expensive to get a good level of coverage using Selenium alone. We try get good coverage using MVP+mock testig and then reserve selenium tests to exercise a smaller number "high value" scenarios -- Cheers, Peter Donald -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
