How many testers receive a software for testing without any idea of the process previously involved in the creation? These testers are not specialists, a true specialist will eager to be involved on all stages of the process starting from the requirements stage/design stage, why ?
Because the specialist tester understands that software bugs and bottlenecks will be reduced based on the time he starts to raise is inputs, starting early will give him the power to make real changes that he probably cannot do if he starts is tests on later stages, and that’s not all, based on skillful analyze that start on earlier stages the specialist tester will understand the full picture and that’s allowed him to master many aspects from the QA side, among those aspects we can find:
- Software technical knowledge.
- Why the clients/company decides to develop it?
- The solution we provide to our clients.
- Clients use cases that impact our risk management.
- Allocate the relevant team for testing based on technical and personal strange.
- Design and create a batter test plan.
- Select the most appropriate testing methodology (Agile, Waterfall, V-Model…).
- Create an efficient test case.
- Understand the project scale and manage the version risks.
- Acquire the environment for tests.
- Reduce the amount of defects on future development and testing cycles.
- Save time and money that will be spent for every defect that we failed to find on our ‘Static’ testing and discovered on the “Dynamic” part.
And let me tell you one more thing, if you are reading this post and come up with the conclusion that the author is wrong because he cannot understand the daily pressure you have at your work on a daily basis or in a worst cases scenario you simply failed to understand the urgency of QA involvement on earlier stages of the software life cycle you probably will never be a true specialist in our world.