Most of the organizations these days understand the importance of unit testing and use it heavily in their project. Unit testing frameworks are available for most of the high-level languages like JUnit for Java, NUnit for .NET, pyunit for Python and so on. These unit testing tools have now reached a level of maturity and most of us have probably used them in some capacity. Unit testing Java Script is unfortunately, still a bit tricky and its integration with other tools is also not well known. In this article, I will try to explore how QUnit framework for testing Java Script can be integrated with Selenium and continuous Integration.

Testing web application is always fun and if you are automating your web application testing with Selenium, its even more fun. Unfortunately, like any other tool selenium has few limitations. One of the most annoying limitation of selenium is its inability to handle browser windows (Or any other expected or unexpected windows). When we automate any application which launches these windows (For example security warning windows, certifications windows and so on), we get stuck by the inability of selenium to handle them. I have seen people executing those automated tests but clicking on OK/Yes/Continue manually whenever these windows appear. This defies the whole purpose of automation, because tests can not be executed without human intervention.

Twill is an open source library that allows user to browse the Web from standard command line interface or from Python scripts. This library is written in Python and can be extremely useful for test automation for web applications. Unlike many test automation tools for web application testing, Twill does not launch or need browser. Twill works from the command line (or from your Python script) and allows you to perform standard operations like navigating to specific pages, use forms, cookies and so on. As mentioned earlier, Twill does not launch real browser and hence its usage as test automation tool is limited. Twill can not be used to test rendering of pages, functionality related to Java scripts and so on. Tools like Selenium are better suited for that purpose. Twill is better suited for validating functionality which can be exercised using http request / response and analyzing page source.

This month (17'Th March 2009) TestingGeek team hosted a workshop in BCS SIGSIT conference in London, UK. This workshop was aimed for the people working in Agile environment and using Selenium.

This workshop will give you basic understanding of what is Agile, how testing is different in Agile world and how Selenium can be used to automate effectively in Agile world.

 

Selenium Grid allows you to distribute your tests on multiple machines so that you can run your tests in parallel on different browsers. The same results could be achieved using Hudson slaves and maven builds. In this article we will talk about using Hudson to kick off your automated tests on different machines and on different browsers. Before we go on and start talking about setting up slave build machines we will first understand what is Hudson and what is meant by Hudson slaves.

Last month TestingGeek team hosted a workshop in BCS SIGSIT conference in London, UK. This workshop was aimed for the novice Selenium users and was well received by all the audience.

This workshop will give you basic understanding of Selenium IDE and RC. Also, how open source has affected Selenium and its development. We have also touched upon briefly Ruby and how it is used in the context of Selenium RC.

If you work in web application testing, you probably know that Selenium is one of the best tool for automating web applications. Though it can be used to test various aspects of web application, sometime you need to find your way around when using Selenium, one such situation is testing flash component using Selenium. Developers use Flash to beautify their websites, but it makes test automation a challenging task because Selenium can not read or record any actions on flash objects.

In the previous Selenium articles, we discussed what is Selenium and how Selenium IDE can be used to automate your web applications. We also learnt about the limitations of Selenium IDE in terms of language support (Only Selenese ) and browser support (Firefox only) . These limitations can be diminished by using Selenium Remote Control. Read more...