As many of you may be already aware, almost all new QA positions are requiring Test Automation skill set.
What doest that mean? It simply means that you must be a developer with the solid knowledge to testing frameworks.
At a minimum, this is what nowadays most leading companies are expecting from this role. Even during phone screening you will get passed on the question what is a test case or test plan and be most likely asked how to write a sort algorithm on an array without using conventional bubble or quick sort algorithms.
As agile becomes common practice in most large companies and startups, solid line between developer and QA roles becomes very blur. Developer and Tester becomes one single role. I.e., Developer opens pull request with some code for a new feature or a bug fix, and at the same time add a unit + functional test to the same pull request.
So what is going to happen to Manual Testers? Is this role dead? The answer is NOT. The manual tester will always be needed. Without human eyes it is impossible to release bug-free software! It is the fact and it is very hard to ignore! I’ve recently spoke with Zenefits, a leader in HR software for smaller firms, and their lead DevOps told me that Zenefits’ model of 0 testers on the team started failing once the company has begun to scale.
However, manual testing is already shifting towards cheaper alternative – crowd testing. Check Utest.com if you are interested. Plus due to technological break though in test automation frameworks, a number of manual testers drastically dropped from 1 tester per every 2-3 developer to 1:8 ration.
If you in a position of manual tester, what should you do? You should:
If you are confused where to start, BayQATraining is here to help you. The company conducts 100% hands-on bootcamps to address industry demand. Join bootcamps to break your fear and shift your career to next level: Schedule of courses.