The solution is scalable because it covers a large range of platforms.

My impressions of the scalability are that it is top shelf.

I can tell you how many people that I have integrated it with in the company, I would say thousands. Our company is worldwide, and Eggplant is used throughout the company and in multiple facets. The team that I'm currently working with has 14 testers right there. And if you throw the devs in, that's 20 devs that are using it. Then you're looking at 34, not counting the previous team of 10, so that's 44. The team before that was five. Let's round it up to 50 people that I've interacted with just on that alone. But Eggplant is used across the company, so I'd have to say a thousand plus. You could talk to Keysight and ask them how many people use it at Northrop Grumman and they could give you a number.

We have plans to increase the usage. I'll probably integrate it into the next team I go to. I'm kind of the unofficial spokesman slash salesman for Eggplant. That's my job, basically working in test automation. I'm an automation engineer and it's phenomenal for the turnover rate that you can turnover tests with. If the next team I go to are all developers and they brought me in to integrate a GUI automation solution, and the team doesn't have a lot of money, then maybe we'd have to go with a cheaper solution. But I've been fortunate to land on teams where they have the budget for that. Let's be honest, Eggplant isn't cheap.

I'm pretty sure it's scalable but I've never thought of it in those terms. We had two or three hands-on users who worked with Eggplant on a daily basis; we were all working on testing. 

In terms of scalability, since I'm writing functions, it's as fast as I can write them.

About eight months ago, we were going to have a fourth person work on it. They didn't want to get an extra license so we were having to work around the fact that we only had three licenses, but potentially four people working on it. However, given our setup, I could see that it would be easy to add another license if that's what we truly needed and get somebody up and running fairly quickly.

The roles of our users are two QA people and one intern. What they're doing is very similar to what I'm doing. The intern is working closely with me, doing a lot of the tests that I just haven't had time for. On our website we have four sub-domains. I would start the intern on the basics and then she would be able to completely write all of the smoke tests at least, and the basic code tests for that, no problem.

The other QA is the person who is using it through the VM because of the need for the Oracle system. He's also been using that for full integration testing, setting up data, verifying that it goes through, and that it gets the expected result at the end. He's also the one who is working on performance. He wants to start having the equivalent of hundreds of users hitting it to see how well our systems do.

In terms of maintenance of the solution, I handle all the DAI upgrades on the server as needed, but there isn't a lot of maintenance involved. I believe there are three updates a year. It's just a matter of letting everybody know how to redownload and install it. I've updated DAI once and it went very smoothly and worked well. I have a weekly meeting with one of their technical people and for the DAI update I said to them, "Hey, here's my plan," and made sure that it looked good to them, but I was the one who enacted it.

In terms of general runtime and being able to do whatever we need to do, anything that we have wanted to do for our tests, we've been able to get Eggplant to do it for us. We have mainly gotten some smoke and other automated tests going. We want to ramp up with more of those, but the area that we really need to expand into is reporting. Management is going to want some better reports than we've been giving them but we just haven't had time to look at that aspect, because we have wanted to keep going with the tests, first and foremost. We give them a little "okay," or we give them numbers, rather than providing actual reports. We do want to get to that eventually because I know the solution has that capability.

One of my customers is using Eggplant Test currently.

We haven't tried to scale. In my company, we made applications just for Android and iOS. I use just those functions. I use just small kinds of functions.

The limit of Eggplant is, due to the specific language, the scalability is not good. For example, Selenium supports many languages, including Java, Java script, or Python and so on, however, Eggplant doesn't support other languages. 

We have between ten and 20 users of the solution right now. There may be other teams and users at other offices in other countries. 

The scalability of the solution is good, we did not encounter any problems.

We have certified people in our company using this solution.

We want to increase our usage in the future, but at this time we are able to deliver our objectives.

I also haven't found any issues as far as scalability goes. We've expanded the usage from our original use case and have quadrupled the utilization, at least, across some other use cases within our organization. We're always looking for areas where we could expand and continue to grow our use of Eggplant.

I currently have five people using the solutions and they're all data analysts.

For us, scalability is related to the licensing cost problem. If you have only two licenses and can't afford a third one or a fourth one, the scalability is limited. In terms of the system itself, it's perfect. You can change and share a script, or processes, or actions. But you can't grow within a company when you're limited by the number of executable licenses because of the price.

The solution is based on a Windows model, where adding users is just a few clicks. It is easy to manage users and add them.

It is scalable, but it is a matter of money in the pocket. You can scale it, but then you have to have additional licenses. The licensing approach of eggPlant is not the best. 

We had licence errors even when we had the correct licences and we got connection issues as well when trying to scale.

It is easily scalable. We have about seven users who are using this solution. We don't have any plans to increase its usage.