Blogs

It seems that no matter how much you look for information about Eclipse and how to setup different types of projects, your version Eclipse is innevitably not the same version of the person who makes the tutorial and nor are you as much of an Eclipse geek as the writer of the tutorial. The same things will probably be thought about what follows

First of all I am doing this in Eclipse 3.3 WTP.

I started by creating a new Java project.

Which should have resulted in a basic project that looks something like this.

Then right click on the project root and choose “Properties” from the context menu (Alt+Enter). Go to the “Java Build Path” section of the properties. There you can include source files from elsewhere on your computer - so for example if you keep your test code elsewhere on your system you can include the source folder which will include your Java files in the Java project so that they can be built and run as a Java program while still keeping the files in your source control folder as well. This way you also avoid checking in Java projects all over the place that are useless for everyone else.

Now we add some external Jars. Find the Selenium Java client Jar and the JUnit Jar on your system and add them.

Now your project should be ready to go and you can create Selenium tests using the Java API and run them from Eclipse using JUnit. How sweet it is!

We are getting really close to being able to release all of our Selenium functional tests and JSUnit unit tests to our developer community! Ryan has been doing a kick ass job of bring Cruise Control back from the brink and we are being way better about actually running all our tests

With Cruise Control we can now check out our web based dashboard to see the results of automagical test runs and builds or do a manual build. We can even see the results of our Java based Selenium functional tests online.

By abstracting much of the Ajax and DOM leg work into base classes we get really clean Java based functional tests that look something like this:
clickCell(2,2);
assertEquals("Some cell value", getSelectedCellValue());

What could be easier? It is also nice that it is run from Java since I can just create a Java project that references all my Ajax tests then compile and run them individually on my development computer using JUnit. Then they can also easily be called from ANT build files and Cruise Control as well.

I will be posting some more about Ajax testing soon.