When say “no” to automated testing?

by Helen Johnson | June 6, 2018 9:57 am

Despite providing a number of advantages, automation of software testing applied to the “improper” project may cause a failure of software release. To avoid such a scenario, you should know when it is better to conduct manual testing instead of test automation.

First of all, automated testing[1] is a rather challenging process as different factors may complicate the process of scripts development. Besides, there are test cases that you’d better not to automate as your effort won’t be justified. Let’s review what tests shouldn’t be automated.

Dynamic elements of websites

JavaScript code, Flash and Silverlight containers, secondary browser windows and other dynamic elements of a website make it difficult to automate the validation of the whole page as well as some of its elements. For example, if you have a website constructor or online editor – software with a drag&drop feature – then the development of automated tests will take some time. Besides, the quality and coverage of such tests will be put into question.

Flash and Silverlight are used to develop multimedia applications that can be implemented in a web page code in a form of special container. Users don’t see anything that happens inside the container. Special engines process the elements. So you don’t have direct access to those elements, and you cannot write scripts. To know more about automation of web testing, watch our webinar[2].

Mobile test automation

The mobile test automation market is still under development, and nowadays the solutions for mobile testing are rather limited. Appium has some errors and restrictions that prevent effective automation of mobile applications. It is challenging to automate such features as:

Software with complex logic

You can spend hundred hours on automating the verification of particular functionality, but at the end, your tests may fail. And in the majority of cases, it turns out that manual verification of this feature will be less time and resource consuming.

Media content

You cannot automate the verification of media content, e.g., audio and video files. Nevertheless, libraries and frameworks with Artificial Intelligence[3] elements do exist. But you can apply them to very specific tasks. You can describe the logic that will work in case of system states predefined. But you won’t discover bugs using such scripts. Human needs a second to make sure that a video has started or that image size was changed. There is no need to check all that using test scripts.

Related Posts:

  1. automated testing: http://qatestlab.com/services/test-automation/
  2. webinar: http://qatestlab.com/resources/webinars/automation-of-web-testing/
  3. Artificial Intelligence: http://blog.qatestlab.com/2018/05/16/artificial-intelligence-adoption/
  4. What projects need test automation: http://blog.qatestlab.com/2018/06/12/when-automate-testing/
  5. Software Test Automation: Problems and Tips: http://blog.qatestlab.com/2017/01/04/automation-problems-tips/
  6. How to Choose a Tool for Automated Testing?: http://blog.qatestlab.com/2016/09/16/choose-automation-tool/
  7. Test Automation: Planning and Winning: http://blog.qatestlab.com/2016/07/08/test-automation-planning/
  8. Test Automation: Cleaning Up Your Test Scripts: http://blog.qatestlab.com/2016/06/30/automated-test-scripts/

Source URL: http://blog.qatestlab.com/2018/06/06/no-automated-testing/