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
With TDD etc we are all assuming that we have a healthy test suite. Now some researchers from the Netherlands and Belgium have published a way to actaully measure this
. Their idea is to plot
- on one axis the percentage of the total code base that is test rather than production code and
- on the other axis the test coverage.
In a healthy project, they argue, the coverage should increase or at least not decrease while the test code percentage grows or does not decrease.
C.A. Middleburg of the University of Amsterdam has conducted a literature survey to find out about the state of the art in software testing theory. I will quote one of his conclusions here:
Some remarkable observations are:
- in the development of existing theories about software testing, what sets
software testing apart from other forms of software analysis, namely that a
test involves the execution of code and observation of effects of the execution,
is completely forgotten;
It is rather remarkable, isn’t it?
#agile, #projectmanagement, #ehealth, #mhealth #phr, #professionalism, #SoftwareEngineering