RPA tools vs Test automation tools (Selenium-TestComplete...)

Hello,
I dont really understand what is the difference between RPA tools vs Test automation tools (Selenium-TestComplete…). I guess that RPA is more for automating a bussiness processes and test automation tools are for automating the tests for some product/app.
Am I right? If so, These scenarios are very different from each other so I guess that there are also some situations where the use of one or the other can be compatible?

1 Like

Hi Carlos!

RPA tools comes in different types, some are better at some things than others. Similarly it has to do with the tool stack of the system under test.

Claissic big names RPA tools mostly focus on automating business processes. For standard systems (enterprise grade like SAP, dynamics 365 etc) and for legacy systems - some of the RPA tools could be relevant to consider. see article below.

If your system under test is web only, and you have the source code - use the classic test automation tools. If it’s web, but you don’t have the code base perhaps testim.io and cypress.io is relevant for your end to end tests. Consider if you have the classic layers of the test pyramid available.

If you prefer to build a codebase of test on top of SAP, RoboCloud/Robot Framework has some options too.

2 Likes

Thanks for your answer Jesper. When you said “If your system under test is web only, and you have the source code - use the classic test automation tools” I was wondering: Why if your system under test is web only? :slight_smile:

first of all, if the system under test is web only, there is no need to spend 1000’s of $£€ on the big name commercial RPA tools. :smiley: Their strength is more on processing automation of tedious end user business tasks and where the testing goes across things on the desktop (outside the browser) … (and systems without an available code base)

If your system under test is web only, you can follow the modern testing principles and build in Observability in (https://charity.wtf/) and a lot of the things in the code. Plenty of best practices around ci/cd for web systems. Obviously it depends on how well the knowledge about the system is codified - but you can work on that within your org/team too.

It’s more tricky of the source code of your web SUT is not available to you and render new locators every time you deploy or refresh. … for that consider to move up the stack and use cypress or testim.

IMHO :slight_smile:

1 Like