I needed to run some selenium tests written by a Java team using maven

I ran into a couple of errors

Annotations are not supported in -source 1.3

I wanted to write some automated tests for CSS changes and bugs, these type of issues are quite prone to regression so re-running the tests has a large benefit.

It is possible to add new assertions to selenium via the user-extensions.js file

The following adds a test for computed style, this only works in firefox as far as I know - but some automation is better than none

I wasn’t 100% clear from the docs how to implement rollup rules in selenium ui-elements and searching the web didn’t return much - so here’s an example in case it’s helpful to others.

Add this to the user-extensions.js file

While playing around with selenium IDE I discovered a fantatsic tool that makes test (and results) more readable while making the suite of tests easier to adapt to layout changes.

What it does is to allow you to centrally define most of the xpath (and related) statements and give page elements meaningful names.

One of the nice things about selenium tests is that you get a clean browser session each time (so no problems with cookies etc left over from earlier)

But the way this is achieved is by using a new profile each time and this profile doesn’t know about your SSL exceptions for avoiding error messages with those self-signed certs on the dev server.

This causes access to SSL via selenium to fail.

Hudson http://hudson-ci.org/ is a continuous integration server - it runs and monitors ‘jobs’ in a way that is useful to regularly build software and report on any errors.

Selenium http://seleniumhq.org/ is a suite of tools specifically for testing web applications - it tests the full website by automating the running of one or more browsers (so you can test all that pointy clicky ajaxy stuff)

Oh cool :-)

I just noticed that selenium IDE has the option to export tests as PHP unit tests.

As well as following standards such as those laid down by www.w3.org I always try and test websites I develop across a range of browsers. Despite improvements in compatibility in recent years, browsers do still vary in implementation and even relatively minor browsers are still used by large numbers of people.

However all this testing can be hard to keep on top of and sometimes I just have to push out what seems like a small code change with only limited testing.

I’m aiming to automate as much testing as possible, this is a little more work up front - but makes re-running tests trivial and so more likely to happen.