´Why is it, that testing slows us down?´
If I would have gotten a doll$r for everytime I heard such comments 'I would have been a millionaire by now!'
The answer is actually quiet easy. And I can explain it with 2 pictures:
Take into account:
- You need different kind of personalities/characters.
- You need different kind of expertise (code tester, unit tester, system tester, functional tester, acceptance tester, usability tester)
performance tester, security tester, and so on and so fort,
Take into account that chronological testing of aspects might be needed. (first this, then that)
Take into account that the order of this chronological testing can change overtime.
Take into account that not everything can be test automated.
Applying test automation only brings down the pressure on testing for a certain percentage %. (which can be a very very small percentage sometimes, depends on many things)
These are only 2 aspects being mentioned so far and there are many many more!
The bigger the software package, the more software testers you need. But there is a turning point to my opinion which is around 9. (Then you need to do do some other actions.)
8 testers is optimal.
'You mean to say I need 8 software testers?'
Well, depending on the size of the software package, Yes you do!
Minimal is 4, optimal is 8. Less then 4 is like playing chess without all the pieces.
But how many testers do I need for every programmer that I have?
Well... It doesn't work that way... you need all chess pieces to begin with playing chess.
(In other words, you can have 1 programmer and 4 testers, you can have 4 programmers and 4 testers... but actually you can't have 1 programmer and 1 tester, because on the test part you're missing out on chess pieces in that case.)
You wonder why I think all this is? What my vision is based on? Go to 'Contact' tab. Send me an e-mail and I will explain my vision.
(Visit is possible only for companies in the Netherlands)
Op zoek naar testwerk? kijk hier verder:
Uw banner ook hier?