Why is it Necessary to Refactor Automated Tests?

June 26 10:00 2015  

It is known that during test-driven development writing of a small part of code is followed by verifying this part by means of automated tests that are prepared beforehand.

This programming method is considered to be effective, but software engineers sometimes face difficulties. Among frequent problems are long, cumbersome automated tests. Their maintenance may consume more time than all the other works including writing code, performing automated testing and correcting the found errors.

Specialists in unit testing, integration testing, system testing say that it is necessary to refactor automated tests.

Refactoring has been actively used in programming more than a decade. One can find books and articles describing patterns and methods of refactoring, common code smells and so on. It is useful for programmers and automated test engineers to familiarize with them. But the techniques aren’t effective if they are blindly followed, in particular during refactoring of automated tests.

Refactoring Automated Tests One Should:

  • simplify the tests, where it is possible;
  • find and analyses code smells, remove them, where possible;
  • apply only suitable refactoring methods;
  • make sure that after refactoring the tests work as intended.

Automated tests increase productivity of any development process and mobile application testing, desktop testing, web site testing if they are created and maintained properly.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles

Related Articles