Monday, November 17, 2008

Mounting a Lacie NAS under OpenSuse Linux

After a bit of a struggle I found out how to mount a Lacie (Samba) NAS under OpenSuse.
There are two ways to mount it, for both ways it is needed to create a mount point directory. I created a directory called lacie under /mnt . This means the NAS can be reached via /mnt/lacie.
You can do it by hand, but temporarily, as follows:
sudo mount -t cifs -o username=the-username,password=the-password // /mnt/lacie
However, if you want it to be mounted automatically each time you boot, then you need to add a line to the file /etc/fstab:
1) in the console, enter: kdesu kwrite /etc/fstab to edit the file (assuming you run KDE)
2) add a line simular to this line:
// /mnt/lacie cifs
username=the-username,password=the-password,uid=0,gid=0 0 0

Selenium IDE and flow control

For some tests we use Selenium IDE, a Firefox plugin which can be used for easy front-end testing. The tool lacks support for flow control, which we needed. Luckily somebody created an extension:
Selenium flow control

Sunday, November 16, 2008


Currently I am setting up an old Thinkpad laptop as a build and web server. For this task I installed the OpenSuse Linux distro on it. By switching to Linux I stumbled into problems as a noisy fan and not being able to update the BIOS. Luckily Google helped me out by unveiling the Think Wiki web site. This site is aimed at Linux Thinkpad users and has tons of useful information.

Wednesday, November 12, 2008

Wicket, Ajax panels and hung threads

The system administrators:
- Why is your application using much CPU and much memory? And what's up with these hung thread alerts in the server log?
The test team:
- Why is the application so slow?
The programmers:
- we don't know!
After a while we found out. The application its main page contains several Ajax panels, most of them can be typed as containers of 'nice to have information'. In some test cases one of the Ajax panels kept showing: clip_image001. It is something you do not mind if it doesn't block the flow you're in. It turned out that this little animated gif hid an infinite loop that was caused by unexpected output from a web service.
Lesson learned: keep an eye on those friendly looking animated waiting gifs! They might just be hiding a monster!