-
Alert Dialogs Do Not Appear When Using WebDriverBackedSeleniu
With Selenium 1, JavaScript alert and confirmation dialogs were intercepted by the Selenium JavaScript library so they never appeared on-screen and were accessed using selenium.isAlertPresent(), selenium.isConfirmationPresent(), selenium.chooseOkOnNext…
-
Testing@LMAX – Introducing ElementSpecification
Today LMAX Exchange has released ElementSpecification, a very small library we built to make working with selectors in selenium/WebDriver tests easier. It has three main aims:Make it easier to understand selectors by using a very English-like syntaxAvo…
-
Speaking at GeeCON Prague 2015
In this talk we reveal how we develop software. We cover all aspects from our design philosophy, how we practice agile to our continuous integration pipeline and show how far you can go with automatically testing everything.
-
The implicit cast you were not expecting in Java
When you learn Java or any other programming language you usually start by looking at the basics of the type system and how the arithmetic operations work.  You learn how numbers are represented and what types of numbers your programming language o…
-
Improving journalling latency
For the last few months at LMAX Exchange, we’ve been working on building out our next generation platform. Every few years we refresh our hardware and upgrade the machines that run our systems, and this time we decided to have a look at upgrading the o…
-
Swarming
Over the years there has been much lively debate over what constitutes best practise in software development. Whilst this is a topic that people clearly feel strongly about and one that has received a lot of attention there has never really been an industry wide consensus on the subject. Given that people have been developing software in one form or another for nearly eighty years (or considerably longer if you include people that lacked any working hardware on which to run it) you’d think we’d have figured out how to do it by now. The reason we haven’t, probably has something to do with the fact that different situations have different needs and that those needs evolve over time. Individual taste, fashion and the desire of pundits to sell more books may also be implicated. The relentless grind of technology change is probably a relatively minor factor.
“ Here at LMAX Exchange we use a number of software development practises that work very well for us. Many of these we pretty much use all the time. Others are employed frequently if a little more selectively. One practise that falls into this category is swarming. †-
The moving finger writes…
The LMAX Exchange software platform has been in development for a few years now. We have a great development team who are exceptionally talented and productive, so it’s not surprising that we have built up a reasonably large code base. The core exchange is a few million lines of Java and we have a lot […]