Release Management

Wednesday, January 2, 2008

Selenium drops out

Selenium drops out of the race by not so obvious reason as Borland SilkTest 2006. First of all different tools exists under the name Selenium: Selenium IDE, Selenium Core, and Selenium RC. I only tried Selenium RC with Selenium IDE. Selenium Core does not work for us, because it needs to be installed on the same website as application for post release validation.

There are two major drawbacks with using Selenium vs Canoo WebTest. The tool is kind of slow, I run the same tests with Canoo WebTest and they at least a few times faster and this is very critical for us. Next issue is integration with LuntBuild, Selenium requires the browser, while WebTest tests are just a bunch of ANT tasks, so in the future we can easily integrate them to continuous integration process.

Labels:

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]



<< Home


All posts in one place

  • Doxygen vs JavaDoc
  • Installing JNetDirect's JSQLConnect driver
  • Finding problems in Java code wtih PMD
  • Log4j best practices
  • Can't open activity db: Permission denied error for SVN commits
  • Jira Subversion Plugin
  • Implementing Subversion post-commit hook
  • Troubleshooting Subversion and TortoiseSVN
  • IIS 6.0 does not serve files with .docx
  • Installing ANT on Windows XP
  • Luntbuild dealing with SMTP response 554
  • Confluence and Jira OutOfMemory errors
  •