Decoding Tester's mindset
Measuring quality is important, and that's why software testers are to software what the immune system is to the human body. The concept of measuring quality can be a hot-button topic for many software testers. This is because metrics can be used poorly; we've all heard stories about testers who were evaluated based on how many bugs they found or how many automated tests they wrote. These measures have absolutely no bearing on software quality. A person who finds a bug in three different browsers can either write up the bug once or write up a bug for each browser; having three JIRA tickets instead of one makes no difference in what the bug is. The tester doesn’t just compare what happens against the results you expect. This makes testing seem like it is straightforward and mindless.
The tester not only thinks technically, creatively, and analytically. The tester is also a practical thinker, he puts idea into practice. Picture yourself as the test manager, you have 2 testers alongside you. The business needs to have tested a release by a certain time so the project is in schedule - What do you do? One thing that can be done is identify the issues that can happen, prioritise them by their likelihood of happening and their impact, and emphasise the highest priority tests during execution.
Thinking testers adopt a more fitting and flexible approach to testing. Thinking testers delve into the unspoken assumptions and subject the product to a series of tests to determine its stability under different contexts and circumstances. Thinking testers are known to question the current testing methodologies and frameworks in order to find out the best-suited approach to a testing project. They will combine several different approaches to come up with a customized and suitable approach specific to the context of a project.
