testing sucks

Bet that got your attention. It’s true, but let me qualify it: Running test cases over and over in the hope that bugs will manifest sucks. It’s boring, uncreative work and since half the world thinks that is all testing is about, it is no great wonder few people covet testing positions. Testing is either too tedious and repetitive or it’s downright too hard. Either way, who would want to stay in such a position?

What is interesting about testing is strategy, deciding what to test and how to combine multiple features and environmental consideration in a single test. The tactical part of testing, actually running test cases and logging bugs is the least interesting part.

Smart test managers and test directors need to recognize this and ensure that every tester splits their time between strategy and tactics. Take the tedious and repetitive parts of the testing process and automate them. Tool development is a major creative task at Microsoft and is well rewarded by the corporate culture.

For the hard parts of the testing process like deciding what to test and determining test completeness, user scenarios and so forth we have another creative and interesting task. Testers who spend time categorizing tests and developing strategy (the interesting part) are more focused on testing and thus spend less time running tests (the boring part).

Testing is an immature science. There are a lot of insights that a thinking person can make without inordinate effort. By ensuring that testers have the time to take a step back from their testing effort and find insights that will improve their testing, teams will benefit. Not only are such insights liable to improve the overall quality of the test, but the creative time will improve the morale of the testers involved.

So all the managers out there need to ask themselves what they’ve done lately to make their testers more creative. If you don’t have an answer, then testing isn’t the only thing that sucks.

Comments (8)

  1. Onlangs was ik op het Microsoft Application Platform event waar ik een breakout-sessie bijwoonde over

  2. MSDN Archive says:

    Cool, a comment in Dutch (I think). Anyway, maybe it says that I am going to be speaking at the Dutch Developer Days in Holland in May. I hope it does, because that is what I am going to do.

    I wonder how you say ‘sucks’ in Dutch?

  3. Chrishel says:

    ‘sucks’ in Dutch is ‘zuigt’


  4. Tindalos says:

    I work in safety-critical embedded systems, usually as a developer, but sometimes as a tester. Trying to generate the test cases required is (to coin a phrase) a bloody bind. However, it is neccessary, and we do the best we can.

    The only satisfaction I get from this is when I catch some weird edge case. (Un?)fortunately, our engineers are damned good, and these situations are rare.

  5. 之前寫過一篇 給新手 想選擇軟體測試工程師的文章. 對軟體測試工程師的工作做了一點很簡單的介紹希望能破除一些誤解多讓一些有志之士加入軟體測試的行列, 但內容有點過於簡單, 所以再補一篇. 不過這次我想直接介紹軟體測試界的大師,

  6. tarnnum_gupta says:

    I need to ask one very simple question:

    What would you prefer – manual testing or automated testing? why?

  7. Sandee Netha says:

    Ha ha ha

    superb stuff. Nice posting. Keep posting


  8. Roller Press Machine says:

    Its sucks but not always some times it interesting or we can say that adventures when you poke to developer…..