Back to Quality Excites

After one year, again, I will be on Quality Excites Conference as a speaker. Year ago I talked about Jenkins – very powerful tool for Continuous Integration and more. This time I will talk about Scala and how we can improve our Selenium tests using this language in comparison with the popular Java. I will also focus on ScalaTest – in my opinion the best framework for unit tests.

Quality Excites is held in Gliwice on 30th May, it’s free and still you have a chance to register on the official page.

I’m going to prepare also some posts about this topic.

May 2015

Selenium: Simple waitFor method

In the last post about Selenium and waitFor issues I mentioned about automatically refreshing web pages. There was an example with list of the elements which is refreshed in every 5 seconds. Here is a very very simple method which waits for some time for a particular element on the list and when it appear the test continues.


August 2014

Automatic Spell Checker for Web Applications with JUnit report


Some time ago in my project at BLStream we wanted to be sure that texts on web pages are correct and do not have any typos. We did not find any tool which could be easily added to our continuous integration process. I wrote a small script in Ruby which checks every word displayed on the page and then generates JUnit report, thanks to that in Jenkins we have nice graph with test results.


August 2014

Selenium and dynamic Web Applications once again

waterBefore I wrote about dynamic Web Applications and SeleniumWait library to solve issues related to waiting for a dynamically appearing elements. In specific applications we can encounter also another problem – dynamic refreshing. A good example is a list of the elements which are automatically refreshed e.g. every 5 seconds (by JavaScript). Thanks to that user does not need to refresh it manually when she waits for new element.

Unfortunately Selenium has problems with dynamic refreshing and the result is:

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document


org.openqa.selenium.StaleElementReferenceException: Element is no longer attached to the DOM


August 2014

SeleniumWait library to solve issues in dynamic Web Applications

Nowadays there are more and more Web Applications which use JavaScript and AJAX. As a result almost all content on the page are generate or fetch dynamically. Every Test Automation Engineer had a problem with that and saw such exception:

org.openqa.selenium.NoSuchElementException: no such element

It almost always means that such element has not yet appeared on the page and we have to wait for it. Fortunately Selenium gave us WebDriverWait which we should use.


August 2014