Tag Archives: one-liner test cases

How detailled should a test case be?

I sort of remembered a very interesting article about one-liner test cases at testzonen.se. I have blogged about it before, but perhaps it is worth repeating myself? The idea is that detailled (manual, scripted) test cases are uninteresting, limit creativity and are expensive to maintain. The solution is to create “one liner” test cases instead. What about test documentation? If testing actions are recorded during execution then the documentation can be created afterwards.

I guess this goes to show that there is no one size fits all in testing. The right tool should be used at the right time to reach the right goal – which of course is to find bugs early rather than late.

One-liner test cases

There are many kinds of testing. Detailled scripted manual test cases are quite popular but an article at testzonen.se might be an eye-opener if that is your favourite kind of test case. According to the article, these test cases are a waste of time and effort and demeaning to the testers. Instead they advocate a form of test cases which they call “one liners”.

This is quite contrary to the trend towards automated testing which I have written about so often before… Or is it? I guess the main lessons to be learned here are:

  • There are a lot of different test tools, methods, practices, conventions etc
  • Each of them has different advantages and disadvantages, risks and rewards
  • It is important to choose the right one for the right situation
  • Which requires expertise
  • But in the end, any testing is probably better than no testing