The Zen of UI Testing with Selenium, Hudson and Sauce Labs

Most people who write UIs don’t care about testing. You know why? Because it’s hard. So hard, they’d rather not even bother and test things manually. You have multiple browsers. You have multiple platforms. And worse, you have all these frameworks and toolkits which are difficult to test. I’ll pick on GWT here for a moment. It takes 20 seconds to start a test – let alone a server side component to interact with or the time it takes to run your test.

Testing AJAX: Selenium’s ElementNotFoundException

motif

com.thoughtworks.selenium.SeleniumException: ERROR: Element bla bla bla not found

Ok. Face the music. Let’s debug.

Check list:

  • Is locator well defined? Yes. √
  • The element is rendered? Yes.√
  • Do I have any error when I execute code step by step? No.χ
  • Am I crazy? Perhaps. But the problem continues to be there and I have no clue why!!!

What is happening here?

Page Models: An Object Oriented approach to integration tests design

motif

When your test base can be measured in tens of tests (or more) you should pay attention to bests practices and design principles if you want a highly maintainable code, quite resistant to technological changes, changes on the UI, etc. This article introduces Page Model pattern that is a great help in that regard.

Web Testing & Selenium

motif

Why are GUI integration tests needed? On which testing tool technology should I base my tests? What are the cost/benefit of the choosing one over the other? In this brief article we will give you a quick look at the answers to those questions.