The creator of Hudson, Kohsuke Kawaguchi, speaks to Digg engineering team about the current state of Hudson and what we can look forward to down the road. His comments about Selenium and Hudson are of particular interest to the QA team. There are all kinds of integration possibilities – from custom reports that include embedded Sauce Labs video results to automatically establishing connections between our environments, there are lots of ways to make tests run more often and more quickly through Hudson.
In this presentation the Artifactory team demonstrates the benefits of managing your software development life-cycle through continuous integration. Frederic Simon and Yoav Landman show how to automate large-scale multi-module projects using a fully-integrated platform with Artifactory and Hudson. Using Maven, Gradle, or Ivy builds, it is now possible to dynamically automate and manage the pyramidal stacks of Unit, Functional, and Integration Tests. This demo-based session will show you how Artifactory and Hudson work together to make it much easier to promote certified builds to milestone releases, and finally to general availability, while making sure all builds are fully reproducible.
Continuous Integration is a software development practice where members of a team integrate their work frequently. Each integration is verified by an automated build to find problems as quickly as possible. Many teams discover that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. In our talk, we’ll show how our team uses open-source tools, particularly Selenium Grid and Hudson, to test the web applications we make. Raymond Etornam will cover how we moved from testing them using basic Selenium IDE in Selenese/PHP to a more structured system, where our tests are run using Hudson and Selenium Grid, in Python. Stephen Donner will co-lead, providing more of the historical background.
Paul King presents some of the tools helping one programming in Groovy: Cobertura – code coverage, CodeNarc – code style, EasyB – acceptance tests, GroovyDoc – documentation, GroovyMock/Spock – mocking and testing, Hudson – CI builds, Maven/Ant/Gant/Gradle – build files, OSGi – bundles, and Spring/Guice – dependency injection.
San Francisco Java User Group presents Chris Bedford who talks about:
- How to write functional tests with Selenium (including explaining its IDE, architecture, RC, and alternatives like Canoo WebTest)
- How to set up Selenium testing for web apps in continuous integration using Maven, Ant, Cargo, etc.
- How to use Hudson for build server
San Francisco Java User Group presents Kohsuke Kawaguchi from Sun who introduces us to Hudson, an open-source continuous integration (CI) system, which improves the productivity of a development team by automating various things.
Continuous integration expert Paul Duvall explains how to download, install and configure Hudson and Tomcat, run an HSQL database, run an Ant automated build, use Subversion to manage source files and administer the Hudson web application.
In this video Uncle Bob shows how he set up Hudson to be the continuous integration server for FitNesse.
In this episode we will continue taking a look at how to setup the Hudson build server for usage in a .net environment. We will be taking a look at how we can use Hudson to report our Unit Tests results after each build. We will be looking at both reporting NUnit and MSTest results and will also show how you can convert MSTest results into NUnit results in order to report all tests in a single screen.
In this episode we will take a look at how to setup the Hudson build server for our application. We will start off by showing how simple it is to install Hudson and then walk through various configuration points in the server. Finally we will end up by creating a simple build which pulls from SVN and runs our Nant script.