Author: Alfonso Alarcón

Automated testing is a process to test the functionalities of a software (application, web, mobile,…) taking the role of an end-user to identify any unexpected behavior or bug.  In this way of working the tester writes scripts and uses specialized software such as Visual Studio, HP UFT, AutoIt, Ranorex Studio, FlaUI, SeeTest, Squish or Selenium among hundreds of others. It is used to re-run test scenarios that were performed manually, more quickly and repeatedly.

Automated testing should be used by considering the following aspects:

  • Large and critical projects
  • Projects that require testing the same areas frequently
  • Requirements that do not change frequently
  • Availability of time

Automated testing is part of the global process of testing: testingpiramide

Following the ISTQB documentation, automated testing provides the next benefits:

  • More test can be run per build
  • The possibility to create test that cannot be done manually
  • Test can be more complex
  • Test run faster
  • Test are less subject to operator error
  • More effective and efficient use of testing resources
  • Quicker feedback regarding software quality
  • Improved system reliability
  • Improved consistency of test

On the other hand, the disadvantages are:

  • Additional costs are involved
  • Requires additional technologies
  • Team needs to have development and automation skills
  • On-going test automation solution maintenance requirement
  • Can distract from testing objectives (focusing on automating test cases at the expense of executing test)
  • Test can become more complex
  • addtional errors may be introduced by automation

This is the first post of a sequence that can be read consecutively. Please, read the next:

All-in-one strategy. Merging automation technologies: Post to explain a philosophy of working that is based on an IDE (as Visual Studio) completed with plugins of others free automation technologies.

Layer structure for automated testing projects: Post to create an automation project with a very simply layer structure.

Other related posts:

Misunderstanding in automated testing:  Post about some incorrect ideas that people have about automated testing.

Automation testing principles​: Post about basic principles that must be considered when implement an automation project.

The post are linked as follows:

documentscheme