Scalability is fabulous.

We've certainly taken on more projects. When I first started about nine years ago, there was one major implementation at a time. At the moment we have about six major projects going on and, with the unwinding due to the spinoff, there are probably about 50, but those are not being tested with automated software. We're focusing on just the two SAP ERPs, S/4, and the ancillary web apps. It does allow them to implement faster. Since we did the Middle East, they've brought up two new companies in six months, which is amazing for them. It probably would have been one at a time over a year and a half or two years, otherwise.

We don't use Certify to create RPA at this point. We have so many ERPs to automate that we're sticking to that right now. We're trying to get to where we can pick up more licenses and build up the team so we can start doing some of these other things. Right now, with the spin-off from our parent, everybody is hyper-focused on unwinding. When you're part of a big organization like we were — we're still pretty big but we were huge, Fortune 50 — and you start unwinding things, there are so many shared services and servers that are on their domain, etc. It's going to take us two to three years to unwind all that. So we're marching ahead on our ERPs and I'm keeping my head down. I have my seven licenses, although I want to get about 10 more, but I'm not going to raise my hand until we get unwound.

I would rate the scalability ten out of ten. At the moment, we are involved in four distinct projects out of the overall portfolio, which consists of around thirty projects. The focus is primarily on high-scale business initiatives.

Worksoft Certify is a scalable solution. I rate Worksoft Certify a seven out of ten for scalability.

Because we started early with the tool, it took us a while. I feel like we almost glued things together as our needs became more. The capability that was delivered by Worksoft was there. Therefore, there hasn't been a time when they have been behind me when I have needed something that wasn't available.

I am expecting it will the same in the RPA space. We will grow together because of our close partnership, and if there is a gap, I can work with them to figure out what the best approach is to close it. I think we will be able to stay with the tool for a long time because of its scalability.

I don't have the words to express its scalability besides awesome. The amount of changes that we have seen are tremendous.

At our peak usage, we have had seven people working on it, and have had no issues with that. Now, with our current work load, we only have three people. We only run our test suite. It was one of my goals on this project that we had the infrastructure setup, so we could always run our entire test suite overnight. As we built out our library, this meant expanding our infrastructure. Right now, we have 100 to 150 integration tests, and some of them can take ten to 20 minutes to run. A single instance of Certify can only run one at a time. Thus, we have had to think about how we set up our infrastructure in such a way that we can run the entire suite of 150 tests in six hours.

The way that we have done this is to split it up amongst servers. Therefore, we still have extra servers for execution. We have four servers now and run the tests in batches of about six queued up at a time. In this way, we can run our suite of 150 in parallel across four machines and get it done in about six hours. Right now, we do this manually. We do the manual breaking up and monitoring. I know Worksoft has some tools which automate this. This is something that is on our radar to look at as we grow. However, right now, we just manually manage the process.

We have three test developers using it. These are the people actually building tests. In terms of consumers of the test automation, we have probably 35 to 40 business analyst.

The solution is scalable. In my project, we have a team of around 100 people, 20 of whom are using Worksoft. We have a dedicated automation team. To date, we have automated more than 3,000 test cases using Worksoft.

Worksoft Certify is scalable, and I'm giving its stability a rating of four out of five.

The solution enabled us to scale up testing because we don't need to use manually testing. We are also using it for project testing. 

There are overall 12 to 13 users. We have three users identified for test automation. We have another 10 users who use different packages from models of SAP. They use it to capture their processes.

Its scalability is very good. We are a very big organization. In my team, we have close to 14 automation engineers, but there are so many other projects where Worksoft is used. I don't know the exact number, but it would be very high. Its usage is not extensive because it is mostly being used for ERP applications. 

In my previous organization also, it was implemented for many projects.

We have seen the customers starting their automation journey from zero test scripts to 8000 or 10,000 scripts. We have seen that Worksoft is able to scale up, then run thousands of test scripts concurrently and deliver value.

One of our customers has about 10 SAP applications with about 70 plus non-SAP applications. So, we automate approximately 80 SAP and non-SAP applications using Worksoft Certify.

We have learned the scalability part over time. We were very successful with SAP, but not very successful with the web. Over the period of about two years, we were able to prove to our company that we can use Worksoft for different type of applications. While there is a learning curve, it is all about trying things out and failing few times before you get a success.

I am confident that Certify can scale to fit our automation testing needs as we expand the current automation testing framework across the wider Johnson Matthey application landscape. We are also exploring options to identify potential areas where Certify can help support mass data uploads, etc. to benefit other teams in their day to day operations.

We have several concurrent users accessing Certify in our environment, primarily automation engineers, test engineers and tech managers.

The tool's scalability features did meet my company's goals. Scalability-wise, I rate the solution a seven to eight out of ten.

Because it is three times faster than manual testing, we can test more with fewer people. That gives us operational scalability already. Platform also has the Execution Manager tool if we would like to have technical scalability via a cluster of virtual machines. In addition Certify itself supports multi-agents, APIs, and integration with Jenkins and other applications including PowerShell. That means we can also develop scalable setup ourselves

As for overall scalability of Certify, licensing is the main bottleneck. You cannot scale more than you have licenses for. You cannot uplift your digital workforce just for one month and run 300 nodes strong cluster for a big upgrade tests. It is not different for majority of IT products, we don't see much of a problem for now.

Certify is our main tool for test automation for ERP, for PLM, and HR. It's covering two major applications that are at the core of any big machinery or manufacturing corporation. We continuously increase the scope, because systems are developed and extended.

It's fairly easy to scale, which is a nice thing. Once you create what I will call a sub-process, if you want to use that sub-process in many other processes, it's really easy to use. For us, that's what makes it scalable. You can use that same process wherever you need it. The use of the recordsets just allows us to be able to change the data that make it unique and that make it easily maintained. It's very easy to scale. It simplifies our workflow.

I love its scalability. I like records set that you can just add onto it. We are going into a new country every year and the ability to increase from test scripts makes the product so much simpler.

It scales well. We have eight offshore people and four developers in New York. We can add developers as needed. With the offshore team, we've have at least 20 people trained on Worksoft, but eight people actively on the team now.

We have about a 1000 active users with about 5000 users total. However, this includes all of the employees and their self-service.

This is a scalable solution. 

We are using it on quite a large scale. If we have a requirement for the new development, we have to use Certify. My project involves maintenance and new development. In the maintenance phase, we have regression testing. We have created a batch file, and when we are doing the regression testing, we are executing this batch file. So, we are using it for day-to-day activities. We are also using another tool from Worksoft called Worksoft Execution Manager.

The number of users working on this solution varies based on the project timeline and the number of scripts. For example, if the client's requirements need to be delivered in a very short period of time, then instead of four resources, I will take eight resources.

In terms of scalability, we only have a few licenses. We manage and maintain the underlying database actively to avoid scalability issues. We are confident that Worksoft Certify can scale to fit our automation testing needs as we:

• Scale-up with many more automated tests of varying length
• Scale-out with unattended lights-out execution.

Worksoft has good scalability. This is also the reason why we easily can automate for our new laptops.

We have increased the number of tests that we run based on customer requirements.

Worksoft Certify is a highly scalable solution. However, it was a bit slower compared to the other automation tools. For example, Tricentis Tosca is providing major competition to Worksoft Certify and they are slightly a better tool. Whenever Worksoft Certify faces any challenges they're providing some patches to fix them, and that is helping the automation to grow faster and more efficiently. We have the layouts and plenty of recordsets that make Worksoft Certify more scalable.  

It is very scalable.

The solution hasn't enabled us to scale up testing yet. We're on the way forward, but because of some issues in our own architecture we are not able to execute those tests. But I know how the setup is working, and I think you can scale up really easily; just add more machines, add more users, and have a go.

When I started within the program itself, no one else was using it. There were two users on the Railnova team. At this moment, about 10 or 12 people are using but within a couple of months we will be around 50 users in total.

Scalability is closely linked to stability. If Worksoft Certify is stable, then it's easily scalable, and if it's not stable, then it's still scalable, but every time, you have to make some adjustments.

The scalability is really good. We had just talked with Worksoft about if there were any limits in terms of how long your scripts can run for or how many can be running at one time on the database. It seems the only concern is the hardware that you are running it on.

Scalability is throttled in part by the system that you are testing. So, how much testing can your system handle? 

I think they came out with a different type of licensing specifically for testing. Therefore, you don't have to use a more expensive user license, you can use an automation license. So potentially, if we had 100 use cases, we could spin up a 100 different machines, have them all run and be done in five minutes. That would be the goal, but I don't know if that would actually succeed or not.

The solution will enable us to scale up our testing. With our focus being more on regression testing, it increases the testing of existing functionality first, and then we'll bring in that new functionality.

We are planning on rolling this out to more people, multiples of the number we have using it today. We think that it should be scalable but we haven't done it yet on that scale so we don't know for sure. But we do feel it will be scalable and that it will scale well.

Our extent of usage is pretty narrow at the moment. Approximately 10 people are using it right now and they are mainly automation engineers. There are a few directors using it to understand what the product is. People who we would consider to be "automation champions," who will help champion the product at our global headquarters, are being trained on it right now. They're not actually going to use the application, they're just going to understand it so they can help champion it and bring it on, full-scale, with user acceptance. 

Our main users in the future will be those information business analysts who know their respective products very well, the ones who are making the changes in targeted areas and who can easily reach out. They will be able to quickly test and record whatever they need to record for testing. We're looking at anywhere between 20 and 50 additional users within the next year, depending on how well user-acceptance goes, and expansion will continue from there.

Scalability is still to be seen. We have seen a lot of performance issues, so I cannot say for now. From a technical standpoint, it seems relatively easy to scale and we have attempted to do so. However our developers report frequent performance issues and system crashes.  We have not made Automator's mode work after one year in Worksoft. So in theory, it works, but if these issues persist, it does not give me the confidence to scale out another 100 projects.

The scalability has been good. At first, we targeted complete automation only for ECC systems. Then, we extended it to CRM and ServiceNow, not only for the North American region, but for the European and Asian regions, as well. Our company is global, and our next regional rollout will be Latin America.

The scalability is good.

It's not very scalable. 

The scalability is working well for our needs.

It scales pretty well.

It is very scalable with users. We have business users who are scripting. We have Worksoft developers who do more complicated work. Then, it moves over to the people who do execution and process through Execution Manager, so we have several different layers of users doing different tasks.

At the moment we don't have any issues with scalability. We have about 300 end users working with Worksoft. On infrastructure, it's split. We have a WTS environment, a Citrix environment, for those colleagues who want to use the prepared environment. We have other colleagues who are using the client on their own machines, on their own laptops or desktops. The only thing that we saw at the beginning which we need to change in the future is that, due to the latency, we cannot use clients in the US, for example, while having the server in Germany.

If the latency is over a certain number of milliseconds then it is basically impossible to do automation. That was one of the main reasons why we set up the Citrix environment at the very beginning.

We are still in the phase within our company, or within IT services, of training and spreading the topic of test automation, overall. So our coverage, at the moment, is not the entire organization, it's only the IT department. Once we have done this - and it will take at least another year - we will see if we spread using Worksoft and our internal corporate tool as a combination, or tool ecosystem, further into the organization. But this is not our not our team's responsibility so it's not really in focus at the moment. We are pushing for test automation in our teams and there is still a huge demand for training and new teams coming into the topic of test automation.

It's been very scalable for us;

Depending on how many licenses, it's all seat licensed. It's not a concurrent license. If you don't have people logged in, more people can't use your licenses from your pool.

You assign those licenses out to people and as you continue to grow, like I was talking about with our virtual machines, we do everything in a virtual environment for all of our Worksoft work.

As we've needed more virtual machines, we've got an image of our Worksoft clients and we just add them into our environment.

We have not encountered any scalability issues.

Worksoft Certify is scalable. However, if the final output were more customizable, it would be even more scalable.

Worksoft Certify is easy to scale. We have somewhere between 60 and 80 people using it at the moment. 

There were no scalability issues.

Worksoft has done a good job keeping abreast with browsers and various different development disciplines. In addition, database size has never been an issue. In fact, as test automation requirements have grown, being built on a database has certainly enabled better management of the automation reservoir of tests, as well as all the components, discipline interfaces, requirements, results, users, security, etc.

We haven't jumped yet to other systems. We are definitely looking into that. There should be no scalability issues.

We came to Worksoft with the hope of doing end-to-end testing. When Worksoft came in, we challenged them for a week to show us that it worked where you jump systems. They literally put people on our site for a week. It was a quick little RFP. We did see it work, so we know it works. We saw it jump back to our CARS system. Literally, we pulled Revitas CARS system up, and it logged into our CARS system, that's a web-based system as well. It started going through the steps that we needed to go through in CARS, then passed the status back to our eCommerce system. So, we know it works for us.

We know that the systems that we have involved will work with the end-to-end testing, but we haven't gone there yet. It's mostly on our side, not the software nor Worksoft. We are just doing other projects right now.

We currently have ten people (tops) using it in our organization. 

It is scalable.

If done properly, it's very scalable. It creates automation which can be run from an SAP point of view. I can create automation which runs in any SAP environment that I want it to run in, as long as the UI is the same.

We expanded licenses after a year.

It is highly scalable and reusable. It is easy for team members to maintain and use with confidence. There is great versatility.

We have 16 applications that we do end-to-end testing using Worksoft.

As of now, there are no scalability issues.

I have not encountered any scalability issues.

We did not encounter any issues with scalability.

No.

There were no scalability issues.

No issues encountered.

This is a scalable solution.

Able to handle large volumes.