Comparison between script-based and module-based approaches for test automation 

Often there’s a doubt which test automation is better suited to our application. Is it the script based approach using classic coding with for example Selenium? Or do I use the module based approach, as offered by Tricentis or UiPath?  
 
The answer – It depends. 
 
Script-based automation mainly uses freeware. Module based test automation, on the other hand, often requires the conclusion of a so-called subscription. 
 
For a consideration, it must be taken into account that test automation inevitably requires maintenance of the automated test cases. 
 
Let’s assume I am planning an application that will be developed further over a longer period of time and the number of automated test cases will constantly increase. In that case, maintenance requires significantly less effort and know-how and it is more likely to use the module-based test automation approach. 

 
If I am planning a smaller and temporally completed application for which the number of test cases to be automated remains rather constant, the script-based approach is recommended if sufficient coding know-how is available.