Joakim, Either tool should work. If you try out Selenium, you'll need to try out the Selenium RC version, which lets you write your tests in Java, Ruby, Python, etc. WebDriver lets you write your tests in Java.
I'd probably use WebDriver if I had to start a new project today - parts of it are getting merged into the next version of Selenium. http://google-opensource.blogspot.com/2009/05/introducing-webdriver.html Since you'll be writing your tests in a programming language like Java, you can do whatever you want with input XML files, but it will be up to you to parse the files just like you would in any other program. As for ensureDebugId, the JavaDoc for UIObject has some documentation about how to use it. http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/gwt/user/client/ui/UIObject.html#ensureDebugId(java.lang.String) Good luck! On Jul 21, 4:22 am, Joakim Sjöberg <joakim.sjob...@artificial- solutions.com> wrote: > Hello Dan! > > Thanks for the answer! I think that right now what we need is a simple > end-to-end smoke test. Witch of WebDriver or > Selenium would you think is the best way to go? Do you know if any of them > have the possibilities of getting > an xml file with data to enter during the testing to run the test with? > > How does the ensureDebugId work? Is that something you add in your GWT > application? > > Many question :) > > Hope to get some answers :) > > // Joakim > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Daniel Wellman > Sent: Monday, July 20, 2009 1:20 PM > To: Google Web Toolkit > Subject: Re: Automatic Testing > > 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-novem... > > 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 > orhttp://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/g... > > 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 -~----------~----~----~----~------~----~------~--~---
