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

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…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…

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…