Sunday, February 16, 2020

Disadvantages of automated functional testing

Disadvantages of Automated Functional Testing

  1. You have to keep your computer unlocked as long as the automated functional tests are running. 
  2. The machine used for running scripts gets occupied until the test automation activity is finished(true for Selenium, Appium, WinAppDriver, CodedUI). 
  3. Small mistakes at the wrong time can fail your automated testing scripts. For example hitting the enter key while UI automated testing is in progress might cause an unwanted popup to open or a form to submit which could lead to a test failure
  4. Automated black box testing (a.k.a functional UI testing) is slow. (true for Selenium, Appium, WinAppDriver, CodedUI)
  5. A lot of resources are needed to run multiple tests in parallel(although it might not be possible to run certain tests in parallel due to application domain requirements).
  6. You can’t pin-point the cause of fault, you only get to know the steps to reproduce and the developers have to find the root cause of the bug later.
  7. Automated functional tests are flaky and they fail due to very small changes in the application UI. 

Automation testing is the buzzword of the day. But we must know that there are some types of test automation which are less useful than some other types of automated testing. 

Not all automated tests are created equal.

The UI driven testing known as end to end testing or functional testing is on the surface easiest to get going. Tools like Selenium, Appium, Coded UI, WinAppDriver, WebDriver.IO, PostMan are in high demand. But there are still some disadvantages of automated UI testing. 

This post briefly sums up those for you. 

The best thing you can do is to automate unit testing and then integration testing. That's where you're going to get the most coverage. 

No comments:

Post a Comment

Feel free to talk back...