Try our new research platform with insights from 80,000+ expert users
reviewer1643907 - PeerSpot reviewer
Senior VP Operations at a media company with 1,001-5,000 employees
Real User
Significantly reduced our testing time while increasing our accuracy, producing extremely precise results
Pros and Cons
  • "The features that we like the most are the developer interface and the ability to quickly develop and deploy tests."
  • "If one area could be improved, it would be some of their documentation. In particular, some of their online help and user support documentation is a little bit out of date and could be revised and updated on a more frequent basis. Other than that, I haven't really found any issues or problems."

What is our primary use case?

We use Eggplant for robotic process automation across several use cases. We primarily use it to test television set-top boxes, and we also use it for some automated content matching and for over-the-top streaming device testing as well.

The automation and the testing that we perform with eggplant is really for automation that allows us to generate data via our products, to validate that the data being generated is what we expect. Our primary use cases are for post-development, operational validation and support.

How has it helped my organization?

We were performing tests on television set-top boxes manually. It would take a person anywhere from 90 minutes to over three hours to perform a given test. It would require them to sit in front of a computer screen and manually perform the test operations. Not only was it resource-intensive, but it resulted in inaccuracies because the tests require certain channel changes or activities to be performed on a set-top box with particular timings. Since there were humans performing the tests, the timing was not always accurate. And there would be issues with missed button pushes. Eggplant allowed us to replace that human work with an automated solution that reduced the time that it took a person to perform the test from upwards of three hours down to a few minutes. It also increased the accuracy to the levels where we are entirely accurate with our timing and tests. We now have an extremely precise and extremely accurate level of testing.

It enables true end-to-end testing of processes that span a wide range of devices and architectures. We have used it for several different scenarios and devices. We use it for automating processes on our products, our company's products are primarily SaaS-type products, and we're able to develop automation that works on our entire suite of products across all of our implementations.

It has also helped to uncover critical bugs that our normal testing would have completely missed. By performing the automated tests that we do, we've been able to perform many more tests than we would have done manually. By being able to cover that much more ground, the tests have resulted in discovering issues that we likely wouldn't have discovered before. We've been able to perform both a broader and deeper level of tests.

The testing that we're doing with Eggplant is in operations, a post-implementation type of validation. The information that we uncover from our tests is used as a feedback loop to our internal technical teams and to our external data partners, allowing them to investigate and resolve the issues that they may have in their production systems. The results of our tests are used to identify potential issues with our data partners' data. They are also used to evaluate the data that we generate in our systems, and those results are fed back to our teams. They take the results of our automated tests and use them to apply fixes and upgrades to our existing systems. We're able to inform our internal and external partners and, in turn, have them improve and stabilize their platforms.

What is most valuable?

The feature that we use most is the optical character recognition. The features that we like the most are the developer interface and the ability to quickly develop and deploy tests.

Although the solution enables you to test any software on any device, from mainframe to browser to mobile, our primary use for Eggplant is robotic process automation. We're not using Eggplant for its original software testing purposes. But we have found that, for all of the devices that we need to use Eggplant for, such as Rokus and Fire TVs, we've been able to use it and have not run into any issues.

What needs improvement?

If one area could be improved, it would be some of their documentation. In particular, some of their online help and user support documentation is a little bit out of date and could be revised and updated on a more frequent basis. Other than that, I haven't really found any issues or problems.

Buyer's Guide
Eggplant Test
April 2025
Learn what your peers think about Eggplant Test. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,190 professionals have used our research since 2012.

For how long have I used the solution?

We have been using Eggplant Digital Automation Intelligence for seven years.

What do I think about the stability of the solution?

I'm very impressed with the stability of the solution. I haven't found any issues there.

What do I think about the scalability of the solution?

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.

How are customer service and support?

Their customer support is really impressive. I would rate them a nine out of 10.

Which solution did I use previously and why did I switch?

We did not have a previous solution.

How was the initial setup?

The initial setup was very straightforward. To get our first use case working in production, it took a matter of days, perhaps a week.

We had a specific use case that we were trying to address. We had an already defined scope of manual testing that we were performing. So our strategy was to identify the first test candidate, by starting with testing of devices that were housed internally, within our building and within our testing lab. We implemented that and validated that the Eggplant software was working as expected on those and then we rolled out the testing to external devices and additional use cases after that.

Deployment and maintenance of Eggplant are done by one person in total, and that is divided between a manager of the analysts and myself.

What about the implementation team?

We did it all ourselves.

What was our ROI?

We've reduced the costs involved in performing the tests that we perform, taking a person from hours down to minutes to perform a test. That has translated directly into return on investment, both in overall cost savings to perform the tests and in our ability to do much more with less.

What's my experience with pricing, setup cost, and licensing?

Depending on your use cases, it's prudent to look around at some other solutions if you feel there are others that offer similar features. If you choose Eggplant, you should evaluate how you're going to use it and make a smart decision about the number of developer- and execution-only licenses you purchase to maximize your budget. We found that going heavier on execution-only licenses has been a way to reduce our costs and maximize our ability to benefit from the software.

Beyond the standard licensing fees there is just the cost of the resources it takes to do the work of utilizing Eggplant. And that is much better than the alternative of manual testing. There are almost negligible hardware costs. We have Eggplant running on commodity workstations that aren't anything special or expensive. I wouldn't consider it a significant expense to host it.

Which other solutions did I evaluate?

We did not evaluate other solutions. We chose Eggplant because they had some documentation and online information that I found during my research that was very specifically geared towards my use case. I found out very quickly how easily and how well it worked to solve the problem that I had. I didn't feel that it warranted any further research.

What other advice do I have?

My advice would be try it before you buy it. They offer a trial copy and you have plenty of time to build some prototypes. The speed at which you can actually be up and running is great, so that during the trial period you can very quickly find out how well the solution is going to meet your needs. See if you can build a prototype that meets your needs quickly and if you can do that, then you're going to be in good shape.

We use the basic, core functionality of Eggplant Digital Automation Intelligence, where we develop tests in the user interface and usually execute them via the command line. We're developing those tests manually to serve our needs. We've had some exploratory sessions on the solution's AI features and that's something that I'm sure we'll be diving into further in the near future. But we have been able to meet most of our needs with the more core functions of the software.

If someone who is not using Eggplant said to me, “We are comfortable with automating 70 percent of our linear paths," I would say that we had a similar quote from our QA manager, seven years ago when I decided to look for a solution. The QA manager was satisfied with what was being done and didn't want to really put forth the effort to look for an additional or different solution from what he had. With a little bit of work, I was able to discover Eggplant as a solution and build a prototype and automate the work that was being done. It was very eye-opening to our company and was received very well. You're doing yourself a disservice if you're not constantly looking for better solutions and improvements in your current processes.

The biggest lesson that I've learned from using Eggplant Digital Automation Intelligence is that it pays to do your research and look for solutions. When you've got a use case or an issue that is presenting itself, do your research and find out what other people are doing and what else is out there that may help with solving the problem at hand. In most cases, you're not the only one who has that problem. Doing some research to see who's doing what and the experiences that others have had with the different solutions out there is a great way to find a good solution like Eggplant.

We've been using this product for quite a while and we've found that it's able to address the use cases that we throw at it. We haven't run into any situations that I'm aware of where we earmarked Eggplant for a solution but were unable to apply it.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
PeerSpot user
Integration Specialist at a financial services firm with 10,001+ employees
Real User
Top 5
A stable solution used for automation testing, but it should improving its offering in non-Windows environments
Pros and Cons
  • "The main feature of Eggplant Test is that it can do fully automated web testing and app testing."
  • "Eggplant Test should emphasize on improving its offering in non-Windows environments."

What is our primary use case?

We use Eggplant Test for automation testing.

What is most valuable?

The main feature of Eggplant Test is that it can do fully automated web testing and app testing.

What needs improvement?

Eggplant Test should emphasize on improving its offering in non-Windows environments. It should be able to switch from one platform to another. Although they offer it on other platforms, the application is more stable or more suited for Windows for now.

For how long have I used the solution?

I have been using Eggplant Test for five years now.

What do I think about the stability of the solution?

Eggplant Test is a stable solution.

What do I think about the scalability of the solution?

One of my customers is using Eggplant Test currently.

How are customer service and support?

The response time of the solution's technical support team is quite slow.

How was the initial setup?

Eggplant Test's initial setup is complex. Initially, when I started working on the solution, its deployment took a very long time. I'm not aware if things have changed with the recent version. My answers are based on my previous experience with the solution.

What's my experience with pricing, setup cost, and licensing?

Eggplant Test is a very expensive solution. It's not suitable for small companies. Instead, it is more suited for big customers.

What other advice do I have?

Around 15 technical staff members are required for the solution's deployment and maintenance.

Users must do a POC before using Eggplant Test.

Overall, I rate Eggplant Test a seven out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
Eggplant Test
April 2025
Learn what your peers think about Eggplant Test. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,190 professionals have used our research since 2012.
QA Engineer at a computer software company with 1,001-5,000 employees
Real User
Easy to set up with useful testing and good reporting features
Pros and Cons
  • "It is easy to set up."
  • "The language is too specific; it is just for Eggplant."

What is our primary use case?

I usually use this to make UI tests. Our company makes an application, a mobile application, and in order to confirm the functionality, I usually use this product for regression or function testing.

What is most valuable?

The recording feature is very helpful. I also like the scripting functionality.

It is easy to set up.

What needs improvement?

The language is too specific; it is just for Eggplant. If they could offer a variety of languages, such as Java or Python, that it would be more helpful. I cannot use Java or Python in Eggplant. I want to use the other languages in Eggplant.

The solution is a bit heavy and can be hard on my laptop.

For how long have I used the solution?

I've been using the solution for a year.

What do I think about the stability of the solution?

The solution is very heavy, so sometimes my laptop, when I use it, stops and I have to link with it again. It may be due to the fact that it is a recording tool.

What do I think about the scalability of the solution?

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. 

How are customer service and support?

There is a health service in the Eggplant tool. When I have a problem, for example, with the latest version of the iOS, I send them an email and then they answer me and provide a solution. I have to send them logs from my computer and then the other things. The team is generally good. they are helpful.

Which solution did I use previously and why did I switch?

I'm interested in automation and API testing, so our company uses tools like Eggplant and Selenium and also SoapUI, and then Postman.

These days I use only Eggplant since it is very easy to use, especially in the function test, and in the UI test. It's better than other tools. 

How was the initial setup?

When I install the Eggplant, they cannot service or support the latest version of iOS. That said, they have had very little time to update their application. In general, it is very easy. The setup process is better than another application.

There's another team that handles the maintenance. 

What about the implementation team?

The solution was set up in-house. 

What other advice do I have?

I'm not sure of the exact version number I'm using. 

Their website is really good, and there is so much information on their website. They have many examples, and then there are many ways to solve problems. There are tutorials for every level of user. Before you buy the tool, you can watch the lectures, and then you can ask them for a POC. For us, they sent us the pilot tools for weeks or months. If you are skilled in UI or function testing, you can try it out.

I'd rate the solution eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user433410 - PeerSpot reviewer
Teamleader Test Software at a healthcare company with 501-1,000 employees
Real User
We can keep all our tests up-to-date all the time
Pros and Cons
  • "We are able to now automate tests, which so far have been manual."
  • "GUI testing is the strength of the tool. The tool works as expected, and the support response from eggPlant, as a company, has been quick and substantial."
  • "A step forward would be to have event support, because it is more or less linear at the moment."

What is our primary use case?

GUI testing is the strength of the tool. We have been satisfied with the tool, and not only the tool, but the service behind it. The tool works as expected, and the response from eggPlant, as a company, has been quick and substantial.

How has it helped my organization?

We are able to now automate tests, which so far have been manual. Now, it is possible to automate them.

What is most valuable?

  • The availability of the support. 
  • The internet presentation: If there are any questions, most of the questions can be answered with the web presentation and documentation. 
  • The strength of the tool is we almost have no unwanted influence on the system of the test, because Eggplant is based on the reality approach. 
  • It can be used for different operating platforms.
  • It is easy to use.

What needs improvement?

A step forward would be to have event support; supporting different events. At the moment, it is more or less linear. We write the code, but from the tool, we do not have support of events in the system. E.g., programming timers where we have different actions in case certain timers expire. If one part of the program is running, we can get a key event. At the moment, we can implement everything in a linear manner, as predicted. 

The world is not linear and can have unpredictable events where you have to react, which should be allowed in a system on a test. The system on a test should be able handle different events at the same time with different elements or servers. At the moment, this is not supported in eggPlant, and it would be a big step forward.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

Stability is okay, and has improved from version to version. However, it has not been 100 percent reached, and it will not be reached as long as the software is being developed, used, and new elements are being introduced. Errors and failures can happen, but if you detect them, the support is quick. 

I had a case that they improved over the weekend. Friday evening, I detected a bug, and by Monday morning, it was corrected. From this standpoint, the stability with the support behind it, I am very satisfied.

What do I think about the scalability of the solution?

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. 

How are customer service and technical support?

The support is good. I would rate the technical support between an eight to nine out of 10.

Which solution did I use previously and why did I switch?

Previously, we used C# based implementation. The reason that we changed was the instability and inflexibility of the tool. If the system on the test has improved and developed, then we needed a test tool which we could adapt in the same or even faster manner. Our previous tool did not help us in this direction. With eggPlant, we have this possibility and can keep all our tests up-to-date all the time.

How was the initial setup?

The initial setup was easy.

What about the implementation team?

I did the initial setup myself.

Which other solutions did I evaluate?

We did evaluate another US vendor, but I have forgotten their name. They reused something which were the property rights on eggPlant's site, which is why we did not select them.

What other advice do I have?

You should be very clear about what your goals are. If you have this, then check the fit and the match. Afterwards, have a trial period and again check how the tool fits. 

When discussing eggPlant, it is important to use it, implement the scenarios, and run the tool in a regression mode, permanently. Then, you can see the benefit of what you have done and what it is improving. Working with it, this is the important part.

The most important criteria when selecting a vendor is the product. The product has to fulfill our requirements. Then, the vendor should be one that we can trust in.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Integration Specialist at a financial services firm with 10,001+ employees
Real User
Top 5
A solution that offers good scripting and OCR, but lacks good reporting functionality
Pros and Cons
  • "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."
  • "The reporting function is a bit shallow. The solution does not offer very comprehensive reporting in terms of your test results. The reporting time and the logs are very high level as well. These areas need improvement."

What is most valuable?

The OCR (Optical Character Cognition) is a very useful feature. It mirrors your phone or your device system.

The scripting is nice and easy to use. The use of the tool is great. You can recreate scripts as well. It can generate scripts based on your actions from the screen.

What needs improvement?

The setup process is quite lengthy. There's a lot of dependencies. Parts of it need to be centralized.

The reporting function is a bit shallow. The solution does not offer very comprehensive reporting in terms of your test results. The reporting time and the logs are very high level as well. These areas need improvement.

For how long have I used the solution?

I've been using the solution for just under a year.

What do I think about the stability of the solution?

The tool is quite stable. The only issue is connectivity. The RDC connection might be problematic, but I think the call tool itself is quite stable. I haven't really experienced a lot of crashing, or time-outs, or things like that. The stability could be affected by the number of resources available.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

I would rate technical support at three out of five. I don't think they have enough coverage for support. The issues take too long to be resolved. There are also relational issues, location issues, or geolocation issues. For example, in my case, when the support person is in America the response will be the day after the ticket was originally issued. It's too slow of a response because the response team is in America.

How was the initial setup?

The installation is easy, but configuration, based on our project at least, is quite extensive.

What about the implementation team?

We implemented the solution ourselves.

What other advice do I have?

Implementation depends on a lot of factors, but you do need a team that has technical knowledge of the tool. There's a lot of configuration involved when you set up the solution.

I would rate the solution seven out of ten.

I am not a fan because of the reporting functionality and the difficulty in configuring the solution.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2018421 - PeerSpot reviewer
Software Engineer at a computer software company with 5,001-10,000 employees
Real User
Effective OCR technology, useful bug hunting, and plenty of documentation
Pros and Cons
  • "The most valuable features of Eggplant Digital Automation Intelligence are bug hunting and OCR technology."
  • "Eggplant Digital Automation Intelligence could improve by lowering the price."

What is our primary use case?

We did a POC using Eggplant Digital Automation Intelligence where we did the model testing and used DI agents.

We use the Eggplant Digital Automation Intelligence for one of our desktop applications where there are graphs, such as PowerPoints and Spotify dashboards. There are some graphs in which we would like to evaluate the data from the tool. First, we have to validate the data from the back end, and then take the value coming from the back end and cross-validate from the graphs. Additionally, we have to edit the PDF files. We use Eggplant Digital Automation Intelligence for validation.

How has it helped my organization?

This solution has helped our organization because we can create test cases faster as compared to using Selenium. There are no language dependencies and people are not required to be trained for two to five months. People can write test cases using Eggplant Digital Automation Intelligence. Using the solution has improved productivity from using Selenium.

What is most valuable?

The most valuable features of Eggplant Digital Automation Intelligence are bug hunting and OCR technology.

What needs improvement?

Eggplant Digital Automation Intelligence could improve by lowering the price.

For how long have I used the solution?

I have been using Eggplant Digital Automation Intelligence for approximately two years.

What do I think about the stability of the solution?

Eggplant Digital Automation Intelligence is a stable solution.

What do I think about the scalability of the solution?

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.

How are customer service and support?

The support from Eggplant Digital Automation Intelligence is supportive of any issue we have had. You only need to raise a request, and they'll help. They can schedule a call to understand the use case and can help resolve it. The customer support is good.

I rate the support a nine out of ten.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We have used multiple different tools. We choose the one that fits the use case the best.

When I compare Eggplant Digital Automation Intelligence to Selenium, the bug hunting, and OCR technology features are good in Eggplant Digital Automation Intelligence.

How was the initial setup?

The initial setup of Eggplant Digital Automation Intelligence is easy. However, you required a person who will guide you on how to install it and everything else. Once you understand then you don't require anyone to help you going forward.

They have their own documentation and customer support that can help you to download everything. Once you have an understanding then you can independently download and use it.

If you compare it with other functionalized automation tools, it's easy. However, some understanding is required to write the test cases.

What about the implementation team?

We had some assistance at the beginning of the implementation.

What was our ROI?

We have received a return on investment.

What's my experience with pricing, setup cost, and licensing?

Eggplant Digital Automation Intelligence is based on user licenses. Other similar tools use different types of licensing models. 

This solution is expensive when compared to the market. However, the reason it is more expensive is because of its stability, high performance, and for its support of any technology.

There are no additional costs other than the licensing.

Which other solutions did I evaluate?

We did not evaluate other options because we knew that for desktop applications, and for the legacy technology we have this solution was the best. 

This solution supports any technology and we did not want to invest our time to crosscheck with other tools. We knew this solution can meet our needs and this is why we choose it.

What other advice do I have?

Eggplant Digital Automation Intelligence is the market leader in AI automation. They independently worked across every technology.

My approach while identifying the tool to use is simple. If you want to see the performance, and you want to improve productivity, then it would be best to choose the commercial tool. If you don't want to improve productivity and want to stay on the same line, it is best to use an open-source solution, such as Selenium. Selenium requires skilled people to use it. Which is very difficult to find in the market at this time. Additionally, it requires a lot of time for maintenance. To reduce all these costs, you should choose a commercial tool. 

My advice to others is to understand the solution very well. Understand your use cases and try to fit them. It is important to see whether your use cases fit into the tool which you are looking for and based on that you can go ahead and use it.

I rate Eggplant Digital Automation Intelligence an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user812943 - PeerSpot reviewer
Lead partner at Selex ES
Real User
It has low productivity, but provides very strong cross-platform support
Pros and Cons
  • "It provides very strong cross-platform support."
  • "It has low productivity."

It has low productivity, but interesting tool features. It provides very strong cross-platform support.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user375345 - PeerSpot reviewer
Senior Test Consultant\Competency Lead at a tech services company with 501-1,000 employees
Consultant
Regression test packs are 70% automated. Integration into JIRA, Mantis, and HP ALM etc. is important as most of us use a combination of them.​

Valuable Features

Object recognition on applications with minimal data input, and the fact that it is designed to run on a machine when you can install automation software on the actual device.

Improvements to My Organization

Prior to using the product, all regression testing was done manually for our POS system. Now regression test packs are 70% automated. We have also integrated eggPlant into HP ALM.

Room for Improvement

eggPlants data input is text based and does not easily conform to data driven test, and this makes data management painful. Integration into other vendor tools are important in today’s market, Even though Vendors would like us to use only their toolset, it is not always possible, Integration into JIRA, Mantis, and HP ALM etc. is important as most of us use a combination of them.

Use of Solution

I've used it for two years.

Deployment Issues

Deployment went smoothly, installed on server and on the client with no problems, and upgrading to new versions were also seamless.

Stability Issues

We did however have problems when we tried running the scripts on multiple machines concurrently.

Scalability Issues

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

Customer Service and Technical Support

Service has been impressive time wise, with basic queries I always got a working answer with more complicated questions (integration or data driven) I would get the “Sales answers” but after speaking to a more senior support person I was given a decent answer.

Initial Setup

The set-up was straightforward.

Implementation Team

We implemented with an in-house team.

Pricing, Setup Cost and Licensing

I think the licencing model needs to be looked at as it is very expensive, other companies are using/looking at multiple models to assist with various sized companies.

Other Solutions Considered

I did evaluate other automation tools, the problem with the other tools is that you had to install it on the machine with the software being tested. At the time eggPlant was the only tool that could be installed on another machine other than the POS machine and create tests and the object recognition and methods were superior at the time.

Other Advice

If the company only writes systems like POS, and GPS – graphical systems, then eggPlant is a great choice. If the company writes a mix of systems POS, SAP, and insurance software, then I would advise you to use a different tool. The other tools are better suited for high data input systems and have built in mechanisms for tables and similar objects.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Eggplant Test Report and get advice and tips from experienced pros sharing their opinions.
Updated: April 2025
Buyer's Guide
Download our free Eggplant Test Report and get advice and tips from experienced pros sharing their opinions.