Can you recommend any best practices for integrating GUIdancer / Jubula into the build environment?
We recommend using a tool or framework for continuous build integration. This tool can then execute tests and evaluate the results. We use Hudson as our continuous build integration framework. Hudson runs on a dedicated test computer, which has a stable environment and configuration. Our tests are run from this machine, with AUT agents running both locally and on other remote test machines. Hudson: checks out the source files from the repository, builds the application, starts the tests, and reports the test results. The most basic smoke tests are run after commits throughout the day, more complex tests are executed every night, and tests with very long execution times are executed over the weekend. In this way, defects can be identified within a short time after they are committed to the repository.
