If you're looking to write unit or integration tests for GWT client code, I've written an article about my experiences here: "Google Web Toolkit: Writing Ajax Applications Test-First" http://blog.danielwellman.com/2008/11/test-first-gwt-article-in-november-2008-better-software-magazine.html
If you've finished your application and want to add simple end-to-end smoke tests, you might want to consider using WebDriver or Selenium. To add temporary DOM IDs which only appear for testing (which will make writing those WebDriver or Selenium tests easier), consider using the method on UIObject called ensureDebugId: http://tinyurl.com/mdwyky or http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/gwt/user/client/ui/UIObject.html#ensureDebugId%28com.google.gwt.dom.client.Element,%20java.lang.String%29 Dan On Jul 20, 5:38 am, Joakim Sjöberg <joakim.sjob...@artificial- solutions.com> wrote: > Hello! > > I have a question that you might be able to answer. We are developing a GWT > application and would like some form of Automatic testing of the > > GWT application. Is there any good way to do this? Could someone please point > me in the right direction? > > Regards > > Joakim Sjöberg > Developer > Artificial Solutions Scandinavia AB --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
