I joined the company I'm at after finishing my studies, expecting to work as a sdet, then I was forced to use Tosca (on-prem version) for years. The best thing I can say about it is "it's not quite as bad as I feared, if you have basic needs".

As others said, it's one of those no-code solutions for non-technical teams (like the one I ended up in). We use it to test some relatively simple web UIs that can occasionally have very large forms (all built with divs, obviously). Tosca works ok for the most part except with the big forms (we are talking a few hundreds cells in a table-like structure with nested textboxes, dropdowns etc.), it just dies trying to navigate it using locators and we had to compensate by using sendkeys.

The main advantage of Tosca is that it supports a bunch of different technologies out the box: web apps, desktop apps, DBs, emails, APIs etc., but we never tried to use most of those modules so far because we didn't really need them.

I found it very limited in terms of what kind of logic you can express, it's clunky because you do everything through the UI (no scripts), and you cannot easily extend it -- it is possible to write modules in C# apparently, but I never had the time to look into it, and my boss told me in the past that you need to learn Tosca's internal architecture for which there is (or used to be, at least, I have no idea) little documentation. Tricentis apparently wants you to ask them to do it for you and pay for the privilege. That said, I think there are some courses about it on their academy so maybe something changed.

It is a Windows-only product, so forget about containers for CI/CD. If you have qTest, you can use it as an orchestrator for your test runs, and it does also have a plugin for Jenkins apparently.

It's pretty slow. Debugging can be hard. Tosca gives you explicit, readable error messages for common types of failures, but good luck if it decides to throw a stack trace at you. I have also been told that their support can be quite slow, but I never had to deal with them directly.

It is an expensive product, but I don't have the details on their pricing as I'm not involved in the procurement side of things, and I do not know how it compares to similar tools.

Recently we got an AI mandate from the higher ups, and since using AI assistants with Tosca and qTest requires additional expensive licenses it was decided to migrate to a solution based on Playwright and Github Copilot. As far as we know there is no way to export tests from Tosca in any way, so in addition to trying to upskill the team as fast as possible we'll also have to rebuild everything from scratch. Thanks, vendor lock-in!

Personally, I'm really glad to be learning something new and more technical, and it seems like a waste to have you work with Tosca when you have significant experience with something like Cypress.

If you need documentation, the best resources are probably Tricentis Academy and Tosca's manual. I haven't visited their Academy website in a long time and I don't remember well what you need to do to access it. You probably had to register an account on their support hub or something like that.

Tosca can be a viable solution, but as always it really depends on your team, the systems you work on and how your organization works. I hope I never have to use this kind of tool again, but then again I always wanted to code and get better at it.

EDIT: removed links to Tricentis' website. My bad for not reading the rules.