My company has five users for the product. 

I give the scalability of the solution an eight out of ten.

In terms of scalability, that's a challenge in Tricentis Tosca. Scaling the solution is quite difficult because it uses only Windows environments, so it's not a good solution for scaling up. Right now, we rely on Windows, but we are moving to the cloud, so scaling Tricentis Tosca would be difficult for us.

The way we are going about it, it is a scalable model. We are looking at reusability. We are trying to put some kind of governance model in place, where we will have people going back to review and analyze how things are being used. We are trying to come up with an assessment framework for Tosca. 

We have some areas that have Ruby. When we go to an area that already has something implemented in Ruby, we have an automation assessment framework from a Ruby perspective, where we ask our Ruby experts to assess their framework. If the assessment comes out that their framework is pretty solid, stable, maintainable, and they have the skillset, we leave it alone. If the assessment comes out that it is not maintainable, people are not using it, it's not providing the value, we recommend using Tosca. In the same way that we have an automation-assessment for Ruby, we are trying to work on some kind of assessment framework for Tosca. If someone has been using Tosca for two years, we want to be able to go in, assess their framework and say, "Hey, here are the things you have been doing that are great. But you don't have any modules that you're reusing. Why is that?" We are working on implementing something like that, which help us with the reusability and maintainability perspective

With every release they are adding great features. This year, we have taken two upgrades and they have added patches for some defects, like the one that caused the problem with the PDFs. We have 12 or 13 incidents that are open, which include three customization requests, that Tricentis is working on with us. But with their every release, they have added features, not just closed defects, but actually added features, which is great. The challenge is that, in a big company like ours, we cannot afford to take every feature release, every upgrade. That creates a lot of work and a lot of testing, because we need to test everything. Tricentis has been able to give us their roadmap and, at this point, we are planning to take on 13.1 which will be around January/February, 2020.

They do a lot of good releases. It's just that at our scale, the way we are operating — we have 200 licenses and I'm pretty sure we'll need more — we cannot afford to take every upgrade.

We still have other applications that we have not finished in terms of setting them up with Tosca. This is going to go through 2020. Then we will be looking at ways of having people go back to the areas where it has been implemented to see how things are going and what was not implemented. When we are deploying Tosca, we are not doing it for all applications. A particular business solution or department might have 50 applications out of which ten might be critical. We have only put Tosca in place for one or two of those, but we put the right structure in place for them to be able to extend it to the other applications. We intend to go back and see if they have been able to extend or if they need help in increasing the automation presence. We do expect to see an increase in automation usage and coverage, moving forward.

We have a team of 250 people on the solution right now. We have five active licenses on five servers. We have mostly testers on the product. 

It is a scalable solution and a powerful tool. I'd rate scalability eight out of ten. 

We likely will increase usage in the future. 

The scalability is pretty good. I would rate it seven out of ten in terms of how easy it would be to expand. 

We have more than eight people using this solution in our organization. It could be a bit more. We do have a client on it as well, and we are working with them.

We have no issues with scalability. We have a solution architect and a few team members who will develop it.

The solution supports a lot of applications and it supports the leading applications. It can scale very well.

We have approximately 80 people using the solution in my organization. However, we are limited by the licensing cost but what we use of the solution we are using it to the maximum.

I scaled it up a few months ago, and it was not a smooth process.

Right now, it's around seventy people are using it in our company. More than that, it should be.

It is a scalable tool. It is extremely scalable.

I would rate Tosca's scalability at eight out of ten. We have 10 users and 10 exemption licenses in our organization. We plan to increase usage in the near future.

The solution is scalable. It is a strong solution for executing test cases concurrently across multiple browsers and devices. It efficiently handles test case execution in parallel, making it faster for hundreds of test cases. It may require a powerful machine with ample processing power and RAM to maintain optimal speed and performance for executing millions of test cases.

Five users are using this solution. We have concurrent licenses.

I rate the solution’s scalability an eight out of ten.

The solution can scale quite well. We have 16 groups using it. I don't know how many individuals are on it, however, it's likely there are five people per team. We usually don't go by user when we're counting.

We do plan to increase usage in the future. We use it quite extensively already. We may be moving some legacy tools over to it. 

In terms of scalability, one of the things I do is challenge people to prove that it doesn't work. It has yet to be proven to me that it doesn't work with something. We've always found a way to be able to do test automation with it.

We have developers and BAs using the tool. We have 16 delivery teams and there are an average of seven people on each team. We require two people for maintenance of the solution. They are test automation engineers. If you're talking about maintaining test cases, everybody on the delivery team is involved. It's in their goals to maintain their test cases for what they deliver, and that includes developers and BAs.

Every day, Tosca is being used more and more. Part of our digital transformation is that we keep growing the tool base and what the test cases are.

There are no issues with the scalability of the product.

I would rate the scalability a nine out of ten. We have enterprise-level customers because this is not ideal for smaller customers. Smaller customers tend to be using open source tools, but actually, to get it to the enterprise level, Tricentis is used a lot.

I have not encountered any scalability issues.; it is very easy to scale.

Tricentis Tosca, it is very scalable. We are using it for end-to-end automation where we are working on completely different types of applications across different technologies. Tricentis Tosca supports more than 160 technologies as of  2018. It supports the majority of the applications generally available outside. You can directly start automating those applications and tools. It is can be easily scaled. We can execute test cases and we are able to automate very well. We are receiving more than 90 percent of coverage with the out-of-the-box Tricentis Tosca.

We have more than 100 users who are utilizing this particular tool. We worked with customers where there are more than 200 licenses, which have started using it. There are different types of licenses and the users are different. We started using this tool for various projects in our application where there are data developers and automation testers. The client started utilizing those test cases for execution.

Tricentis Tosca is the leading solution in the market. They have some competition, such as Selenium and Worksoft Certify. However, I do not find Selenium to be much of a competitor to Tricentis Tosca. Tricentis are investors in Selenium. The Tricentis team's main focus is not on their test applications but focuses on end-to-end automation. It is trying to convey itself as a complete package of test automation where it can perform functional testing automation from a single tool. We see Tricentis Tosca as a complete package solution.

It is scalable because there is no coding, but from an architecture and infrastructure perspective, it is very hard. So, scalability is a problem because the architecture is heavy.

From the automation perspective, Tricentis Tosca's scalability is good. 

The scalability of Tricentis Tosca is good. We can add more users which is easy to do.

We have approximately five people who use the solution in my company.

Scaling up Tricentis Tosca would be an issue for us because of the licensing. As it's an extremely expensive product and we're a smaller organization, we don't need that many licenses, but sometimes it would be great if we could have two licenses because there are other people in the company who were trained and certified to use Tricentis Tosca. The product does provide a multi-user workspace, but we only have one license currently, so only one execution is possible at a time.

This solution is easily scalable.

It is pretty scalable because of the templates. We can have a single template expand into hundreds of test cases, so it is scalable. In my project, we have between 50 and 60 people how are using it.

I rate Tricentis Tosca an eight or nine out of ten for scalability. Around five users in the test automation space are using Tricentis Tosca in our organization.

From a scalability standpoint, if you are needing the data from Excel and Excel has lots of records, it may be difficult. I want to try for more records, basically between 5,000 and 10,000 rows reading from Excel. That is a bit of a tedious process. Right now, it doesn't seem very scalable if you want to read the data directly from Excel or any other file.

In Excel, you have to create the tables, rows, columns every time. Then, you have to read from Excel. You have to create a similar table structure in Tosca. It's a tedious process.

We have eight to ten automation engineers using the solution right now.

We do plan to increase usage in the future.

The solution is stable. We had to scale up since our team size had grown. My company has 20 users for the product. 

If you buy more licenses, it's scalable. 

We just have a single instance, and we have multiple users with different projects.

We have approximately 100 people using this solution in my company.

There have been no scalability issues as of now.

The solution is scalable. 

I am about to test it in a really big way. So far it has scaled to my needs. I am taking it organization- and vendor-wide in the next 6 months. Let’s see what happens when we bring a Cognizant on.

We had in the past, but those are gone in the latest versions. In the beginning there were problems with scaling up, but those are gone as well.

Tricentis Tosca is very scalable. You can easily move from a small test suite to a larger test suit, which I think is pretty good. We about 100 users in the organization.

No issues so far.

It's scaled for our needs so far.

We are using Tricentis Tosca at 100 percent capacity.

Before, we also used Tosca for manual testing. We had, I think, 400 to 800 main users — not at the same time — but we had a lot of users then. If you know the size of your repository, then it's easy to size the server accordingly. Also, when you know your requirements, you should make sure that the infrastructure meets the requirements, then it's easier. 

Because my organization or team only has one or two testers, we don't need to think about scalability. As a result, that product does not need to be scalable in my environment.

The scalability is good. If I had to rate it out of five, I would say that it would be a three-point five to four.

We have anywhere from 500 to 750 people who are using this solution in our organization.

I have not used to to the point where I needed to scale it.

Our entire team is using it, which is more than five people.

No issues.

No

We are rolling it out to five of our companies. We are trying to control things internally but the solution itself is 100% scalable.

The tool is scalable. We have 10 to 15 users.

We haven't implemented Tosca at a large enough scale to really comment on that. 

No issues encountered.

Depends on the Licensing model you take up.

The scalability of the solution is very good. We can expand it if we need to The solution doesn't give us any problems in that sense.

No, not so far. We have around 3500+ TCS.

Not yet - as the environments were always well set up.

We're discussing internally with fully integrate this tool within our business.

No issues encountered.

I have not encountered any scalability issues.

No issues encountered.

We just started – it should be ok.

N/A

It is scalable.

Not now. In previous versions yes, for more than 10,000 test cases.

No. It is pretty easy to add other users, roles, and control access to different areas of the application. In my case we didn't upscale to a great degree but I know this is possible. Large organisations would take advantage of Tosca's utilisation of the common repository with robust check-in/check-out procedures to eliminate the risk of unintended changes.

We did not encounter any issues with scalability.

There were no scalability issues.

We had to do extensive customization on top of their CI/Distributed Execution engine in order to integrate this into our Continuous Delivery pipeline.

Not all of UI elements were managed correctly by regular Tosca functions, we was forced to use Custom Controls for doing that.

No.

Not much. I Haven't faced any such issues until now.

No issues encountered.

It is scalable.

There were no scalability issues.

We've had no issues with scalability.

There were sometimes issues with scalability.

I did not encounter any issues with scalability.