Today the ‘Introducing Selenium 2’ London Selenium Users event was tentatively announced for April 20th 2010. Please visit the event page to register your interest.… Read More »New London Users Event: Introducing Selenium 2
Yesterday Selenium 2 (alpha 1) was released. This is the first release since the Selenium and WebDriver projects started to merge. The main difference is the inclusion of the WebDriver API into Selenium. I’ve put together a small example below that uses the new API to log into two web based e-mail clients and send an e-mail.Read More »Selenium 2 Examples
Hopefully Selenium Grid 1.0.5 will soon be released, with the much anticipated self-healing features that will save me so much time when RCs go AWOL. Looking further ahead, I would like to see some minor improvements to the Selenium Grid Console such as integrating this very handy Greasemonkey script for unregistering Remote Controls and sortable columns. Below is a quick mock-up of how the console could look with these simple changes.Read More »Improving Selenium Grid
The first London Selenium meetup took place on the 11th November. If you weren’t able to make it then due to the success I will be scheduling another one early in the new year.Read More »A Successful First London Selenium Meetup
In order to save files for investigating failures from within TestNG it’s important to have a safe filename that is unique to the test – otherwise you may overwrite important files. I have written the following simple method in Java that is called from a listener with an
ITestResult parameter to construct a unique file name that should be safe on most file systems.
Despite the name, the Selenium RC (Remote Control) server is often run on the same machine as the testing framework, which makes saving screenshots to disk quite easy. If however you are running Selenium RC on a separate machine, or are using Selenium Grid it can become more difficult as the screenshots are also saved on the remote machines.Read More »Capturing screenshots from remote Selenium RC
One of the big differences between Selenium IDE and a Selenium RC solution is the ability to perform ‘soft’ assertions. Selenium IDE users can append commands with
assert to determine whether the test execution should stop when a failure is observed. A popular use for this is to first assert that you are on the correct page (
assertTitle) and then verify elements on the page. If you were only able to
assert then your tests may fail early on, not revealing further failures that may exist.
Due to the impressive response to the first London Selenium Meetup event, I am pleased to announce that I have increased the RSVP limit from… Read More »London Selenium Meetup increases RSVP limit
dragAndDropToObject command works really well in Selenium, however it does have some limitations. One such limitation I came across recently while writing tests for an ExtJS web application: when your destination object is in a scrolling box (and not in view) the command fails.
Automating an ExtJS web application can be difficult due to the dynamic nature of the page. For example, the majority of unique ID attributes in the HTML will be different between builds, which causes problems locating elements reliably. Another issue is selected items from a ComboBox, which is not a normal HTML
<select> element, but an
<input> that is populated from data in a completely separate section of the DOM.