Skip to main content

Continous web testing with Selenium, Maven and Continuum

Wow, nearly a month without posting. I haven't really gotten any good excuses, just lack of stuff to write about, I guess. But for the last week I've been struggling and doing something I find really interesting and useful: Web-testing.

Regular readers will know about my love for Selenium. I still believe that Selenium is the way to go about web-testing.

So, the web application in a project was approaching web-test-worthiness quickly (well, actually it was about a month or two past the point where we should've started doing web-testing). Mind that we were already doing continous integration on the project, so it was only for the reason of not having core-developers breaking any of the stuff being out in the web.

Let me clarify a bit on that last point: Modern web frameworks expose core domain objects way out into the web (like the User.lastName property here in Matt Raible's example).

When core developers refactor Java classes - XML files, property files, JSP files and JavaScript files are not brought along in the equation (especially not in Eclipse).

Breakage caused by these changes will most likely not be discovered in your unit tests. You need web-tests.

There are a number of other good reasons for doing web-testing, like the ever increasing amount of JavaScript in your webapp, and testing the web across different browsers. So web-testing is a Good Thing.

I'm not going to go on about the different strategies for getting continous web-testing implemented. The elements I were after were:

1) Getting Maven to test with Selenium scripts (no, not JUnit tests exported from Selenium IDE)

Now normally, this isn't too hard. Alot of projects out there do web-testing by storing Selenium tests as Java-code - JUnit tests. But the trick here is to get Maven run tests based on tests in the Selenese format - pure html tables with web-browser instructions (they look a bit like Fit-tables).

There is an ant-task for doing this, which in later turns has been converted to a Maven plugin goal: Selenium Maven Plugin's selenese goal. It was originally a seperate plugin called Mavenium, but now the project seems to have been absorbed into the other one.

2) Getting Continuum to run these tests.

Once Maven is running the tests properly, it shouldn't be a problem to get Continuum running these. BUT there's the issue of how the web app should be deployed and started for the Selenium plugin to have something to run on. Cargo was the obvious tool for doing this job, but there were some bumps on the road to getting it working.

3) Getting the tests to run headless

As shown here, with the headless option in the selenium plugin. Anyhow, I ended up not using that plugin-goal, instead just starting Xvfb manually on the Linux box and setting the DISPLAY variable to something like 127.0.0.1:1. Then there was a whole bunch of trouble getting Firefox 2.0 in on Fedora Core 6 and so on.. Yech.

I believe these three requirements have not been met together on many other projects, and this combination has not been properly documented anywhere else. This is perhaps because only recently have the plugins involved matured to such a degree that this process is possible at all. I did try achieving the same goals before the summer, but ran into all sorts of problems with Firefox 2.0 instances not being started correctly and problems using the maven-cargo-plugin.

The closest I ever found was this how-to. But still the example uses Selenium's JUnit test (we want HTML-tests, remember?).

So in the next post I'll put together an example that actually does the whole thing my way. I did run into a couple of problems with cargo that I have not been able to solve (ended up hacking the plugins somewhat), but still the example should work on a general basis. Too tired to make it right now though.

Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone https://github.com/tfnico/config-mr.git mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

config-atom.git
    -> ~/.atom/*

config-mr.git
    -> ~/.mrconfig
    -> ~/.config/mr/*

config-tmuxinator.git  
    -> ~/.tmuxinator/*

config-vim.git
    -> ~/.vimrc
    -> ~/.vim/*

config-bin.git   
    -> ~/bin/*

config-git.git          
    -> ~/.gitconfig

config-tmux.git  
    -> ~/.tmux.conf    

config-zsh.git
    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months.

We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember, building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application?
You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib, or we use it from a CDN, which may be down or unreachable when we want to use the application..

Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some times we get the latest library of master branch and name it with the commit-id in the fi…

Microsoft ups their Git efforts another notch

This week Microsoft announced first class Git support embedded in the coming version of Visual Studio.

Now, it's not completely shocking. We could have seen it coming since Microsoft started offering Git repos on CodePlex, and more recently offering a Git client for TFS. In any case, these are some big news. Scott Hanselman weighs on some features and some more background here.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…