Comments on: Easy Automated Web Application Testing with Hudson and Selenium

By: newbea

newbea — Fri, 08 Jan 2010 12:56:15 +0000

But there is one problem.
The firefox windows which are opened to run the selenium test,does not get closed.
So next time when i run ‘mvn clean verify’ it says:
“Unable to delete directory selenium”

Then if i manually close firefox and again run the command it runs successfully.

Please help me to solve this problem.

By: VARUN

VARUN — Thu, 07 Jan 2010 10:49:25 +0000

Hi i am automating my build with HUDSON and MAVEN.
I am running selenium test after successful deployment.
Please tell me what is the advantage of running selenium server on a separate machine.
And how to do it because as far as i know maven can start selenium server on local host only.

By: Adam Goucher » Blog Archive » A Smattering of Selenium #2

Adam Goucher » Blog Archive » A Smattering of Selenium #2 — Fri, 09 Oct 2009 00:14:06 +0000

[...] Easy Automated Web Application Testing with Hudson and Selenium [...]

By: peterc

peterc — Sat, 03 Oct 2009 10:57:11 +0000

Check out Fitnium and DbFit for Selenium/DB combination

By: Soapbox Rants and Raves » Continuous Deployment with Hudson…

Soapbox Rants and Raves » Continuous Deployment with Hudson… — Thu, 10 Sep 2009 00:24:03 +0000

[...] about Selenium on the Hudson mailing list and found this interesting blog by Ben Rometsch on “Easy Automated Testing with Hudson and Selenium“. I really liked this picture from the article (hopefully it will spark your interest too!) [...]

By: gokhan

gokhan — Thu, 27 Aug 2009 06:26:32 +0000

Deployment to a test webserver is displayed in the image however it is not mentioned how to do it

By: James

James — Sat, 01 Aug 2009 08:39:42 +0000

Very useful post. Hudson and selenium are great tools that can simplify automated testing.

By: sohbet

sohbet — Wed, 10 Jun 2009 11:04:13 +0000

thanks admin good post

By: Kumar McMillan

Kumar McMillan — Wed, 11 Mar 2009 19:42:45 +0000

Hi. I have had a lot of luck using Hudson with Selenium. However, it was a little tricky to get servers to run Firefox headless and set up X Window frame buffers for the screen capturing.

Also, I see in the article and in comments the mention of setting up a database. I've found that I could remove the database simply for the purpose of testing the way the app works in the browser. In other words, a browser is only needed to test JavaScript. Otherwise you are wasting precious test time. Functional tests requiring a database are easier to do without a browser (HTTP get/post, etc, works on the command line). I gave a talk recently about how I approach Ajax testing:

http://farmdev.com/talks/test-ajax/
http://didenko.com/jschi/090226/

By: Scal

Scal — Fri, 06 Mar 2009 08:40:36 +0000

Selenium offers “Grid”, allowing you to run tests in parallel