Skip to main content

Why I keep badgering on about Web Testing..

Lately I've become somewhat obsessed with testing. A specific kind of testing. I'm not quite sure about the term right now, but it's close to system testing, or maybe user testing. Ye know, that kind of black-box testing that makes sure your stuff works from the user's perspective. In web applications (of which I probably do about 90% of the time) they happen to blend in with web tests.

I suppose it started off with last autumn when I put some thoughts on this into my lightning talk at the Smidig 2007 conference. Well, it actually started all the way back in 2006 when I did a lightning talk about Selenium in XP-meetup based on my experiences with Selenium vs. gargantuan use-case descriptions in a project (see slides).



A few months ago I was down visiting a friend in Bonn, Germany. He works for this CMS-vendor/host called WebFactory. I offered him to drop by their workplace and do a quick demo on Selenium, as I figured they're (a) probably doing web applications, and (b) they're probably not doing web testing (in the automated figure o' speech).

Strictly speaking, I didn't actually do the demo; I had my friend do the demo instead. I took some time in advance to teach him how, and naturally he made a much better point of how to use the tool in their shop than I could. Neat sales trick, eh?

Anyhow, one of the guys' impression was "We had no idea it was that easy!", which is the usual response triggered by showing off Selenium. The 10 minute demo eloped into hours of interesting discussion on all things web, testing, JavaScript, Comet, etc, and the whole thing sort of re-invigorated my feeling of that people still do not know enough about web testing, and the world would be a bit better off if more people knew about it.


If you don't know what it is, there it is (in its simplest sense). A Firefox plugin that records your browsing instructions and can replay them later on a lot faster than you can with mouse and keyboard.

A few weeks later I went on to do a 30-minute session on web testing for my current customer's Java developers. Some days later on I held a 2 hour guest lecture in the University of Oslo's open source course.

I figured, hey, I'm starting to get quite good at presenting this web testing stuff. So I piggy-backed my own effort when writing an abstract submitted to this year's JavaZone conference. I have to admit it's not the most academical subject I would've liked to talk about. But I still see people (a) doing web applications, and (b) not automating their tests. I think it's good talk material because it is:

  • Simple and easy to convey
  • Really useful
  • (and I'm not trying to push any proprietary stuff here, I'm not even a Selenium committer)

So that's why I keep badgering on about Selenium and web testing. I could write page after page on web testing, but for now, if you're interested, take a look at the links in this post and take Selenium for a spin if you haven't already (the new 1.0 beta version is pretty sweet). And give me a shout on what you would have me write about next time. For instance:

* How web tests fit into the bigger picture (testing strategies and all that)
* Why I exaggerated when I once said Selenium tests can replace use-cases
* Why manual testing is still important
* Putting Selenium tests into a Continous Integration server (i.e. expanding my last post on the subject)

Comments

  1. I like this post! Nice too see that other people is also interested in automating their tests.. As Uncle Bob says, it's just not humane to let people test what is possible to automate.

    Give it a swing ;)

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...

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...

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...

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...