FitNesse

February 27, 2009

In our current project we use FitNesse to perform integration tests through simple HTML tables separated by the pip character “|”. After refactoring the main website and moving from Javascript onClick() methods to addActionListener, we came across a problem. FitNesse doesn’t,or more specifically the HTMLFixture, execute this properly.

So we are moving over the FitNesse tests which use this JavaScript to Selenium which loads up a browser and executes the tests. This is different to FitNesse which uses a Java implementation of each browser. Although Selenium is slower to run it allows us to cross browser test the JavaScript. Having done this, the way that the SeleniumFixture returns the HTML has caused errors with the XHTML complaince.

FitNesse is a very good testing environment but we have become bogged down with this JavaScript problem. The HTML interface for creating tests allows non-technical QAs to produce integration tests that span modules and projects.


Follow

Get every new post delivered to your Inbox.