Do you have enough QA engineers in your project? Read the article until the end, if there is no QA in your project, and after that ask yourself the same question again – do you need testers in your team or not? And, maybe you need take one more? 🙂

Every businessman or software product owner knows

“it is better and cheaper to find a problem during development process than to fix it in production state.”

If the product has problems, you can receive a lot of negative feedbacks on Google Play, App Store and other platforms. And even worse, you can lose a lot of money. For example, imagine if the store stops working before Black Friday’s sale? It may be very expensive for the company.

There are many examples in history. There is a known bug when Intel’s processors calculated floating-point division incorrectly. Dividing 4195835.0 by 3145727.0 was 1.33374, instead of 1.33382. Intel was forced to replace the processors for everyone. They spend about 475 million dollars.

So, it is very important to test the product before the release. We can use Manual or/and Automated testing. Both test methods have their advantages and disadvantages, we will describe them below.

QA manual testing

Manual testing is the process through which a real QA engineer checks a product without any automation tools as a real user. The engineer checks all application functions and simulates user behavior on various mobile devices, browsers, operation systems and different versions of these systems.

automation manual qa testing codete blog

Benefits of Manual testing:

  • Real feedbackmanual QA can provide a report as a real user, you can easily understand what your users will feel when they use your product;
  • It is cheap in the short-term – you don’t need expensive tools and highly skilled developers;
  • Speed in the short-term – you need time to develop an automated test program;
  • Research on the fly – QA can do free research, not only pre-implemented test cases but as well a little fantasy what your user can do with the service.

Disadvantages of Manual testing:

  • Human factor – real QA can make a mistake;
  • Reuse – it is easier to run a series of automated tests than to verify a project manually after making even small changes;
  • Impossible to do performance test – real QA cannot simulate a large number of users;
  • Expensive and slow in the long-term – manual QA can’t reduce the time for performing test cases but automated test requires less time to run after it is developed.
  • QA engineers can get used to your product and know how it works so the report will be incorrect and you can lose some important feedback.

Automated QA testing

It is a software verification process that includes launching, executing, analyzing and delivering the result automatically through specific tools.

Automated tests are created by Auto QA engineer who creates the program that can automatically verify your software product. In short – we need to create one program that will check another program.
So Auto QA engineers are real highly qualified Software developers.

Benefits of Automated testing:

  • Capability for performance testing – you can quickly simulate a large number of users.
  • It is cheap in the long-term – when test cases are developed you just need to run them, don’t need to spend time to develop them;
  • Speed in the long-term – automated test can be run automatically, without help of a real user;
  • Reusability – test program can be run as many times as you want.

Disadvantages of Automated testing:

  • Expensive tools and developers – automated testing tools are expensive and the price of automated QA engineers is higher than manual;
  • Developing time – it takes some time to write software tests;
  • You can never test a product like a real user;
  • It is difficult to test the UI/UX product;
  • We need to support a test program – if you change some logic, you need to change the way to test the program.

 

automation or manual qa testing

How to reduce the price of QA testing?

It shouldn’t be a surprise for you if I say that a QA is not the only thing that can be skipped and reduced. But I understand the budget is a very important thing for a new product or startup so I will try to provide some “lifehacks” on how to improve the testing process and save money on your project.

Hire at least one QA engineer at the beginning of the project.

I know, you are thinking  “I will hire a QA when the project will be implemented and save money because QA will be needed only for some short time and he/she will check all product in the same time”. Actually, it is not true.

First of all, QA needs some time to understand how the product works. It is a normal situation when business logic is changed during development and documents are deprecated, so it may be difficult to understand what product behavior is correct and what – not correct. Your QA and developers may be confused here. If QA will join the team at the start, he/she will be familiar with the product and the team.

Secondly, in the end, you can detect thousands of errors, it may be difficult to fix them because the product is already ready. Fix for one small error can affect the whole application, it can take a lot of time to get everything right. Additionally, your developers will wait until QA checks the product and you will never know how many developers you need to keep during the testing process because you will never know how many errors QA will find. So it may be very expensive to keep higher skilled developers during testing.

So, let your team find errors quickly during the developing process, it will save development time and quality will be much better.

Developers can create small automated tests themselves.

If Automated QA engineers are too expensive for your project you may let your developers spend some time on writing automated tests inside the app.

Most of the frameworks and technologies contain a lot of automation test tools – it is free in most cases. So you don’t need any additional engineers for that, your developers are already familiar with the product and can implement small tests easily. Additionally, it will be good motivation for them to implement the product more carefully.

It is really one of the cheapest ways to implement automation tests.

Conclusion

Unfortunately, nobody can give you the answer what is better, manual or automated QA testing. Both methods are good in specific situations. You can use the information above to decide what is better for your project.

But one thing is clear: every project must be tested.

Here you can find a very interesting World Quality Report 2018 which details the current situation in the QA industry.

timofey.kovalenko

Lead Android developer, teacher and mentor