Software Testing… The Road Map
Starting with a well-known joke :)
A QA engineer walks into a bar, and orders a beer.
Then he orders 0 beers.
Then he orders 999999999 beers.
Then he orders nothing.
Then he orders -1 beers.
Then he orders NULL beers.
In a nutshell, above “Joke” is the best way to describe someone what’s the testing stands for.
I would say, one of the main keys to success in software testing career and to shine between thousands of peers is to show the ability of simulating the 1: M relationship; a QA Engineer should be able to reproduce hundreds and even thousands of users in terms of different interactions as well as developers weakest points.
Ensuring the quality is a habit for any organization willing to scale up and produce a reputation. And this can be achieved by understanding the different methodologies for software testing, approaches, and types towards a solid experience in this field.
Therefore,
Below figure can introduce you to the main strategies that software testing build on top of
Above strategies can and should be used by software tester and developer to ensure the proper workflow for a product.
Moreover, You can also observe how you can participate in software development lifecycle as a QA Engineer as well as the followed methodology on an organizational level.
Now, after reading, understanding as well as practicing testing fundamentals, you need to introduce yourself to the very first layer of testing.
Manual testing efforts.
A company received a bill for $50,000 from the software tester for his service over a multi-million-dollar application which no one in the company was able to reproduce. The company was stunned with the exorbitant bill for such a short duration of service and demanded an itemized accounting of his charges.
The software tester responded with the itemization:
Bug Report: $1
Knowing where to look: $49,999
Troubleshooting is the skill that you need to develop, grow, and pay more attention to. Knowing the exact root-cause for the problem will solve multiple issues as well as saving development team time which is the most valuable asset they own.
What about a technical depth?
Many titles can lead to software testing, but of course, with different responsibilities in the testing life cycle.
Automation testing is the latest and modernist way of testing and get rid of duplicated workload.
Below figure can introduce you to the automation testing roadmap and the areas that you need to visit and gain some knowledge in
It’s automation, not automagic. — Jim Hazen
I always encourage any QA Engineer to ensure that testing concepts, methods, and knowledge are wrapped up before starting with automation, as automation testing is not more than:
Documenting Manually Written Test Cases and Engineering it in a way the code will be readable understandable and reusable
