We're starting to make pretty heavy use of UI tests via WebDriver (using Cucumber and Capybara). The major stumbling block has been the speed under which they run. Running locally, with the gwt.codesvr parameter, the tests take the better part of an hour which means no one will run them locally. On the CI server, they take about half an hour but they run against a deployed version of the app so it requires the app to be deployed each time they're run.
Does anyone have any suggestions on speeding the tests up? I'm about to investigate a couple of options: 1) While working on a feature, we run the UI tests specifically for that feature only using the gwt.codesvr parameter. When finished, we can do a full GWT compile, then run all the UI tests locally without the gwt.codesvr parameter. 2) Try running the UI tests on the CI server using hosted mode. If this works, it removes the need to deploy the app first. This has another benefit. Right now, we reset the data before each test using an API. If it works in hosted mode, we could simplify this by just replacing the local .bin datastore file before each test. And maybe even have a series of them with different test data for different scenarios. Would appreciate any and all opinions on this along with other suggestions. -- 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.
