Testenvansoftware.nl
  • Blogs
  • Older blogs
  • Wat is testen?
  • Links
  • C# programming language
  • Testing on Youtube
  • test tooling
  • Test Process
  • a test syllabus
  • Ik zoek werk
  • Robot FrameWork
  • coins
  • Blogs
  • Older blogs
  • Wat is testen?
  • Links
  • C# programming language
  • Testing on Youtube
  • test tooling
  • Test Process
  • a test syllabus
  • Ik zoek werk
  • Robot FrameWork
  • coins

Why is it we test but still find big bugs?

3/21/2018

0 Comments

 

´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:
​
Picture
Picture
Picture
​Persons:
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)
but also:
​performance tester, security tester, and so on and so fort, 

​​​Process:
​
​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)







 
​


0 Comments



Leave a Reply.

    Picture
    Picture
    ​

    Uw banner ook hier?
    Tweet @testensoftware
    Follow @testensoftware

    Archives

    August 2022
    July 2022
    May 2022
    January 2022
    November 2021
    October 2021
    May 2021
    April 2021
    August 2020
    July 2020
    June 2020
    April 2020
    March 2020
    February 2020
    January 2020
    May 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    July 2017
    May 2017
    April 2017
    March 2017
    December 2016
    November 2016
    August 2016
    February 2016
    December 2015
    September 2015
    August 2015
    March 2015
    February 2015
    January 2015
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014

    Tweets by testensoftware

    Author

    Motto:
    'Quality is a choice!'

    Categories

    All



    Foto
    De beste boeken over software testen...
    Foto
    Wat een tester nodig heeft...
    Artikelen over software testen... in het Nederlands: infonu.nl
    Picture
    Teach2000 - overhoorprogramma
Powered by Create your own unique website with customizable templates.