How do you explain if an automation engineer or a manual tester is more important to any company? As the Trends in Software testing companies keep on changing as per requirement or the budget of the company.
It’s like with the casino quote “the house always win” - the budget of the company always decide. If it’s important enough, funding will be found. If budget is not available, the requirement needs to be changed.
One trend to point to is based on the book:
That documents how testing practices leads to better business. - in other words, smart testing activities leads to better business, and thus improves the budget of the company.
To me, the testing effort is the most important part. Other roles besides “manual tester” and “engineer” can do testing. Who is best suited for it? - That depends on your technology stack, your way of working and solution under test and other things.
Different domains and different products will have different needs in terms of what is the most efficient way to test it sufficiently. Currently working with canvas based browsers game with high demands of device support and a fire and forget product strategy. The adaptability of humans are vastly superior to the predictability of a computer in our case. If your product is accessed through an API there is no way having the majority of the process being done by error prone humans is more efficient or that manual testing can come close to the coverage of a computer.
It will be interesting to see if remote work during the pandemic will help us discover new ways to work with testing, have not seen them so far as you still lose a lot with remote work for little gain.
As for trends it still is in the Continuous Deployment track as far as I can see. Which basically means shorter cycles, which means less risk introduces, which means that the shift should move from huge regression scope to impact based testing where you cover the changed area and have a small safety net to cover the other parts.
Last week I came across a repeat of another trend. Where a company was doing “DevOps” but the developers did not get access to any kind of operational data. This happened with agile too, where the trend is that you “do agile” or “do devops” but the people that are saying that have no clue of what that means. It’s just a buzz word that looks good on the job ads.
Everybody in QA knows that manual testing as well as automation testing is a vital part of any organization. You are right that automation is gaining interest among people but the need for functionality testing in many ways can not be ignored.
If we talk about trends then hybrid QA engineers are in demand who can do both automation testing and whenever require perform the functional testing also. A fact that we can not automate everything. So, manual testing is obviously required.
Recording the test case execution is not always there. So, to be on a safer side, it is always recommended to have proof that what is passed was actually passed. If somehow the same issue again arises in production.
if we talk about QA testing performed by in startup OR small quality assurance company, from automation testing to functional, integration to regression, UAT and PROD also, is done by limited QA or single QA only. The reason for this could be less budget or small projects etc. They start from requirement analysis followed by writing test cases and validate them.
However, Functionality Testing, Usability Testing and UAT still requires a response from prospective users.
I hope this information is helpful in providing information about trends in QA industry.
As I’ve experienced my company heading more towards “DevOps/Agile” I think we need to head to a more “Quality Assistance” role like what Atlassian has done - https://www.youtube.com/watch?v=yRP29wFqu20&t=32s
One thing that I got out of the Accelerate book was that it might be more beneficial to have developers own more testing and test automation than leave it to QA. This is assuming there is a huge disparity with the number of developers compared to the number of QA in the team. It doesn’t seem to scale if we go “faster” in our software lifecycle and test automation by QA has to keep up with the software changes.
I think it can scale better If QA can help train developers to test better and create test frameworks and other tools that can help developers write test automation faster and more reliably. And when I mean testing, I also see not just functional testing, but help developers with performance/a11y/security/etc… testing as well.
I have yet to change my company culture in this direction so I don’t know HOW to do this, but I think this could be a possible trend. And I think this is compatible with the “Modern Testing Principles” trend as well.