Being a specialist is not a good option on your path to becoming a passionate software tester. If you still need to go into this direction, you need to do it right. This post is based on a remarkable book written by Chad Fowler, The Passionate Programmer.
To be a real specialist in something, it means to be a generalist in that specialty. For example, if you label your self as an experienced web software tester, you need to be able to answer this question:
How would you crash the Chrome browser?
I do not have an immediate answer to this question. But I know that crashing Chrome is a hard task. Millions of users produce a lot of automatic crash reports daily. Making the most apparent attempts already patched.
But as an experienced Chrome user, you must now answer: I do not know. The above answer is a good start. Along with explaining your heuristics, how would you try to crash Chrome:
- Search for Chromium project issues on its Github project page (oh, there is no such page)
- Investigate cmd line options and what they do
All these heuristics could reveal your specialty. Your specialty should be mastery in resolving never seen issues on Chrome. How to become a generalist in Chrome specialty?
One option could be to join the Chromium project and check testing documentation. There is a lot of information to start learning about Chrome internals.
If you are a specialist, you need to be a generalist in that specialty.