Testing Hints & Tips - New Users Read

[Keith Sterling]

There have been a few posts recently from people asking about Windows
7 support and several asking about problems with Fitnium, all of which
came down to problems with scripts. However none of this is wrong,
keep posting your queries I am happy to help and respond the best I
can.

I am currently working out in Chennai, India so have plenty of time in
the evening to post responses.

However I thought I would use this post to explain how Fitnium is
tested, and also provide some guideance on how to post queries

Fitnium is development entirely on my Macs, all running 10.6 Snow
Leopard, however it is tested on several platforms and as many
browsers as possible. The development cycle is pretty much write new
features & unit tests, update the documentation, build and create
release package. The release package is then deployed to a seperate
folder on my Mac and ran as a clean install. The release is also
deployed to Ubuntu 10, Windows XP, Vista and 7 running a VM images.
For all of these installs I run the entire Fitnium Test Suite, so in
terms of test coverage there is approx 86% unit test coverage using
JUnit and 100% Fitnium API coverage using Fitnium itself to test
itself. In addition before a major release I test against the latest
versions of Safari, Firefox, Chrome and IE on the platforms they are
supported. No one has asked for Opera, but I could install it if
required.

So as you can see Fitnium is pretty much tested across all possibly
platforms and browsers

If you come across a problem then I need some basic details to help.
Javascript errors are typically not to do with the platform i.e Mac or
Windows, its more the Selenium support for the browsers internal
Javascript engine.

Therefore to help me resolve your problems more quickly, when you post
a problem I need the following information

Fitnium Version
Java Version
OS Version
Browser Version

I also need to see the error message you are getting. Just a cut and
past from the Fitnium/Fitnesse window will do

I could also do with seeing the Fitnium test you are executing

I to make things really easy, either the public URL of the page you
are testing, or the snippet of HTML that is not working.

For everyone not using Firefox to develop Fitnium in, MOVE NOW, get
Firefox installed and then install Firebug. This is probably the
greatest aid to developing any Selenium based solution. With firebug
installed you can view individual elements and see the id, class, name
and everything else about them that is needed to create Fitnium calls

Hope this helps

Keith