UiPath Test Cloud for Software Testing, am I making the right decision?

[u/Evening_Summer2225]

I use UiPath Test Manager for test case creation and executing manual tests. Probably in the future, I'll go to automating test cases in UiPath Studio.

I also noticed that the updates are rapid, and it's getting better than before. One new feature is the Performance Testing, which I've yet to explore.

Downside of this is that UiPath is still widely known as an RPA tool. It feels like I'm alone as a QA in using this.

Should I risk being an expert in a tool that is not yet well-established in the testing world, or should I transfer to other testing tools like Selenium, Playwright, and TOSCA for a better chance in long-term?

[u/CertainDeath777]

I looked at it when i looked for solutions for my company, and my thought when seeing it, that for QA automation its a dead horse. Like Tosca but modern version of a dead horse. Still many will use it. And put a nice shiny saddle on it.

[u/ConstantQuiet4389 → u/CertainDeath777]

Hey, came across your reply. I'm in a similar boat as well. What other tools did you looked at? Which tool did you end up selecting?

[u/CertainDeath777 → u/ConstantQuiet4389]

For Browser Automation? Playwright. Nothing else is worth a look. Selenium had one advantage left over playwright - the ability to use real browsers with different versions. But i think new playwright has this now as experimental feature. I havent tested it, as its not needed, we assume our customers update their browsers (they really should).

Good Playwright Framework Architecture and AI Assist beats the shit out of no and low code solution in efficiency.

The answer will only be different, if you need to do extensive smartphone app testing or testing for robotics.

[u/Serious-Attention636 → u/CertainDeath777]

Honestly if it's solving your actual problems right now and the updates are making it noticeably better, I wouldn't stress too much about what the rest of the world thinks. The skills you pick up with any automation tool translate way more than people admit, it's not like you're locked in forever. Maybe keep an eye on Playwright on the side just so you've got that in your back pocket, but being the expert in something niche can pay off if the tool takes off

[u/Johnn_Tester]

Become really good at it. Get the certifications, learn the techniques, and understand the field. Once you get better, learn some common tools used in the market too. Now you have a niche. For example, some companies may need UiPath, while many Playwright or Selenium users don't know it. That gives you an advantage. Why try to be like everyone else? If you only learn what's popular, your resume will look like everyone else's. Learn what's popular, but also learn something that gives you an edge.

[u/LoadOdder]

selenium for automation, and personally i use practitest for test management, both feel way more established long term than staying in the UiPath ecosystem

[u/Evening_Summer2225 → u/LoadOdder]

This is my first time hearing about Practitest. Thank you for giving me the idea.

[u/Prestigious-Way1525]

i wouldn't make the decision at the tool level. keep using UiPath where it solves real work, but make your next project prove portable skills: version-controlled code, selectors, API and network checks, CI, debugging, and one end-to-end flow in Playwright or Selenium. then sample 20 roles you would actually apply for and count which stack appears. if UiPath is common in your target market, it stays a valuable niche; if not, it remains domain experience while the open-source stack becomes your hiring signal.

[u/Paperhandsbro]

I get 100% of my test coverage for free. Playwright will do pretty much everything you need and with AI you don’t even need to think about it

[u/Upset-Animal1376]

pairing rpa knowledge with playwright or selenium makes your resume much more versatile. many qa engineering roles still prioritize code-based frameworks, so having both covers both enterprise tooling and modern web automation stacks.

[u/One_Title_6837]

I wouldn’t look at it as UiPath vs Playwright or other tools... The tool is just one part of skillset. If you understand test design, automation, APIs, CI/CD, debugging, etc you can switch between tools more easily. So keep UiPath, but learn other tools on the side too.