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.


Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

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.

A not so short guide to TDD SaltStack formulas

One of the hardest parts about Infrastructure As Code and Configuration Management is establishing a discipline on developing, testing and deploying changes.
Developers follow established practices and tools have been built and perfected over the last decade and a half. On the other hand sysadmins and ops people do not have the same tooling and culture because estensive automation has only become a trend recently.

So if Infrastructure As Code allows you to version the infrastructure your code runs on, what good is it if then there are no tools or established practices to follow?

Luckily the situation is changing and in this post I'm outlining a methodology for test driven development of SaltStack Formulas.

The idea is that with a single command you can run your formula against a matrix of platforms (operating systems) and suites (or configurations). Each cell of the matrix will be tested and the result is a build failure or success much alike to what every half-decent developer of…