Testing web apps with Selenium
Posted: April 9, 2010 Filed under: development, ideas, javaee, maven, WedDev | Tags: Selenium Leave a comment »Doing investigation about the Java Ecosystem this week and I am surprised with the capabilities of a framework called Selenium. Selenium is a robust set of tools that supports rapid development of test automation for web-based applications. Selenium provides a rich set of testing functions specifically geared to the needs of testing of a web application. These operations are highly flexible, allowing many options for locating UI elements and comparing expected test results against real application behavior. Official web site is http://seleniumhq.org/
A short video of what Selenium is capable to do, could be downloaded at http://seleniumhq.org/movies/intro.mov
I googled a little bit so I am suggesting the following videos to start up:
First a series of 4 videos that present a small (~20 min) tutorial based on Eclipse and TestNG. Integrating with Selenium is very easy. The author created a 4 part tutorial. The first part follows here:
Very easy to follow all 4 parts.
Second a great video from the guys at http://buildlackey.com/ showing a lot of theory and practise about Selenium in a 90 minutes video. The quality of the video is very good, the sound clear and the presenter talks in a very comfortable way. Very cool and easy-going. Talks a lot about Selenium and later goes to details about integrating functional test with Apache Maven and doing Continue Integration with Hudson. The video here:
Apache Maven first step, repository central will be blacklisted
Posted: October 29, 2009 Filed under: Προγραμματισμος, javaee, maven | Tags: maven 1 Comment »I am doing some work with Apache Maven 2 today. Never touched this stuff before. I am following a tutorial at IBM developerWorks. However if you sitting behing a proxy you will receive a “repository central will be blacklisted” fatal error. The execution will fail. Although it seems that we are searching for a “I am feeling lucky” google response, this is not the case. I didn’t find a clear answer with the first glance.
If you are facing the same problem we need to set a proxy via the command line like this:
prompt>mvn … -DproxySet=true -DproxyHost=1.2.3.4 -DproxyPort=8080.
Setting the proxy details right is the solution here. You will be able now to create your first archetype.