When do you need automated testing?
Test automation is an important part of software development on any project. While unit and integration testing are systematically implemented in the company, UI automation still raises some questions. In this post, we will briefly outline our vision of UI test automation.
The company has automated testers and we suggest involving them in the following situations:
-
The UI is relatively stable and is not expected to undergo significant changes in the future
-
The UI is extensive and includes a lot of functionality
-
The backend is constantly changing
As practice shows, this typically happens in two cases:
First – the backend is constantly changing due to the need to update the calculation model within the server logic. This may include graphical implementations of mathematical models, economic systems, reporting systems, etc.
Second – when there is increasing load on the backend, requiring continuous improvements and refactoring.
Therefore, UI automation is quite useful if you clearly understand that the backend will be actively changing in the future while the frontend remains unchanged.