It is 2018 and mobile apps are booming. The number of mobile apps is growing faster then mushrooms in the forrest.

​However there seems to be no regulation or laws for it at all.

​Sometimes it looks like mobile apps are asking permission for controll aspects for the mobile Phone for whatever ​they like. (not what the citizens would accept).

Permissions many times doesn't seem to even make any sense at all.
​
Also it is not clear what the persmissions exactly are about....
​(there's 0% possibility to inform yourselfs)
​

​​comsec.provide.badgepermission.read....      yes ofcourse... w.t.@!! ....

The users however don't seem to have any choice....
​If you ​​accept the permissions you can use the app.
​If you ​decline the permissions however... well then you can't use the app.

​This is NOT! how it should work.
​

In the meantime the number of headlines are piling up about the matter. App users are done! with the way things are going at the moment... that is one thing for sure:

https://nos.nl/nieuwsuur/artikel/2224173-facebook-is-de-controle-over-het-eigen-platform-kwijtgeraakt.html
​
​https://finance.yahoo.com/news/zuck-apologizes-cambridge-analytica-scandal-145721682.html

https://finance.yahoo.com/news/mark-zuckerberg-takes-full-page-140622747.html

https://www.yahoo.com/finance/m/e89bd65f-abde-3cef-9160-46d7fbe8c971/ss_mark-warner-says-mark.html

It should be at least possible to select or de-select from a group of permissions which ones i'd like to allow, or not. Currently you can only agree to all or decline to all. What the....

​And herein lays the opportunity for more software testers working at the government. (And also at big companies like Facebook, Twitter, Google, etcetera.) (and they should work together (in synergy)).

​The #number of software testers that is needed, and the number of good schooled, certified and experienced software testers available in the market (fishpool) are allready way to little at this moment. 

​But, if the world wide governments are really serious about such scandals we have had lately, and they really want to STOP! those kind of unhealthy privacy scandals, then they should motivate new students to choose for the course/job of software testing. Otherwise the shortage of software testers in the nearby future will probably be ​​​CATASTROPHIC!!

The privacy scandal like we have seen lately probably will be just a snowflake on the tip of the Iceberg.​

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

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







 
​

TMap, ISEB or ISTQB, they all teach software testers techniques they can apply in their everyday jobs.
There are several test techniques which can proof very usefull from time-to-time. 

​Although some senior testers say: "it's better to learn on the job and from experience". To my opinion it's also very usefull to proof, with certification, that you're able to apply test techniques.

​The way I see it, is that being able to apply test techniques is just one of the rings you can apply when talking about ​'the book of five rings'.

​

What does it even mean when a testers says: "I work according to the book of five rings principle?
​It means that he does whatever it takes to get the facts on the table. When he needs to discuss to a programmer, he asks questions to a programmer. If he needs clarification of requirements, then he asks the questions to the requirements engineer. 
​If he's uncertain about the correct outcome of a test, he  does whatever it takes to take away that uncertainty. 

​In the end he supplies the business with the information that they need and he does whatever it takes to get that information right.