Webdriver integration with Jenkins
I'm relatively new to Selenium and have written a handful of tests using WebDriver in java that are working quite well. I was reading up on continuous integration and there is a lot of mention regarding headless testing. Is this necessary to be able to kick off a suite of webdriver tests after every jenkins build. I can execute my tests via ant so can I have the ant command run from jenkins which will start my tests. Any feedback or experiences would be very appreciated as I'm trying to get my head around this
Jenkins is a service that basically runs a build/shell script. So you can in theory go 3 ways..
1) Use real browsers as a service through Selenium Grid. This is best for cross browser testing for full regression suites or scheduled tests. The downside is it can suffer reliability issues over time.
2) Headless using HTML Unit or PhantomJS. This is good for running smoke tests very fast that can be integrated into the build cycle as part of every developer check in.
3) Automatic provisioning of browsers using the cloud, for example Sauce Labs. (This is ideal, but quite expensive to implement)
Thanks for the reply. Does grid have to be run on the same sever as Jenkins and can the nodes be on different workstations.
The grid can run on the same or different servers. I personally prefer to put them on different virtual machines. This allows them to run on in dependent runtime environments. For example, say you have to upgrade Java or Maven, you don't want to get into a situation where can upgrading a platform for one tool, can break reliability in the other.
Tags for this Thread