Skip to main content

Testing OpenLayers with Selenium (Patch)

To improve the quality of both my sleep and Mappu development I have started using Selenium IDE for automated testing of Mappu's UI.

It was kind of hard at the beginning, being the UI based on Sproutcore which has the annoying habit of changing the controls ids with every page load, but after a while I was able to get it rolling quite nicely. Then I hit a major roadblock: the OpenLayers-based map control wouldn't react to clicks, mousedown, mouseup, fireEvent or anything else I threw at it.

At first I thought I was sending the events to the wrong element (and I was, at the beginning), but after a while I realized there was something else.

So I forked OL and started hacking away. To make a long story short I debugged the OpenLayers code until I figured it out. The details are in this cold and lonely thread on the openlayers-users mailing list.
Honestly I don't know why Selenium IDE is sending that event with negative coords (which is not triggered during normal user interation), but it seems like the fix I came up with is mostly harmless as all the tests still pass.

So if you want to use Selenium and OpenLayers and you're willing to put up with the risk of monkey patching OpenLayers you can just add this fragment of code in your page after OpenLayers has loaded and before using any OpenLayers object:

OpenLayers.Handler.Click.prototype.mousedown=function(evt) {
     if(evt.xy && (evt.xy.x <= 0.0 && evt.xy.y <= 0.0)) {
         return true;
     }
     this.down = this.getEventInfo(evt);
     this.last = this.getEventInfo(evt);
     return true;
 };

Tested with OpenLayer 2.11 and 2.12. Use at your own risk.
Labels:

Comments

Post a Comment

Popular posts from this blog

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in
Post a Comment
Read more

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive. Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.
1 comment
Read more

How to automatically import a ZFS pool built on top of iSCSI devices with systemd

When using ZFS on top of iSCSI devices one needs to deal with the fact that iSCSI devices usually appear late in the boot process. ZFS on the other hand is loaded early and the iSCSI devices are not present at the time ZFS scans available devices for pools to import. This means that not all ZFS pools might be imported after the system has completed boot, even if the underlying devices are present and functional. A quick and dirty solution would be to run  zpool import <poolname> after boot, either manually or from cron. A better, more elegant solution is instead to hook into systemd events and trigger zpool import as soon as the devices are created.
Post a Comment
Read more