We just raised a $30M Series A: Read our story

Eggplant Digital Automation Intelligence OverviewUNIXBusinessApplication

Eggplant Digital Automation Intelligence is the #9 ranked solution in our list of top Test Automation Tools. It is most often compared to Selenium HQ: Eggplant Digital Automation Intelligence vs Selenium HQ

What is Eggplant Digital Automation Intelligence?

A modern AI-assisted approach to test automation that helps you create products that delight users, deliver at DevOps speed, test the full customer experience, test ANY technology, and predict the quantified impact of new product versions on the user before release.

Eggplant Digital Automation Intelligence is also known as Eggplant DAI.

Eggplant Digital Automation Intelligence Buyer's Guide

Download the Eggplant Digital Automation Intelligence Buyer's Guide including reviews and more. Updated: October 2021

Eggplant Digital Automation Intelligence Customers
FUJIFILM Group, NEC Personal Computers
Eggplant Digital Automation Intelligence Video

Pricing Advice

What users are saying about Eggplant Digital Automation Intelligence pricing:
  • "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."
  • "End-to-end testing isn't possible for us because of the licensing problems. It's very expensive, so we only have two development/execution licenses."

Eggplant Digital Automation Intelligence Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Jon Goranson
QA Analyst at a transportation company with 5,001-10,000 employees
Real User
Top 20
Enables end-to-end testing, including smoke tests and several others

Pros and Cons

  • "DAI's newest release allows us to test via scripts rather than models, because we have done 95 percent of our development in functional, not through modeling. I am really happy that then we can use the controller to run scripts rather than having to translate things to models. There are lots of options."
  • "The IDE could be even more full-featured. Because I was a developer, I was very spoiled by either Visual Studio Code or Visual Studio for shortcuts. For example, I was able to say "ctor" and hit Tab and it would create a template of a constructor for me... It would be great, when I want to create a new function, if there were shortcut commands like those that helped create all of the functions, or if there were shortcut features to do any of the complex plans."

What is our primary use case?

The primary reason that we got Eggplant Digital Automation Intelligence is that we have a couple of systems that are run through virtual machines. Everybody who uses it in our company needs to go through a virtual machine. This solution was the only testing system that was able to run that virtual machine and test within it. It was the best that we found.

What we're mostly testing are web pages and Windows apps; Oracle transportation systems. They could have done local installs, but they put them in VMware and this was the best way to test them.

How has it helped my organization?

In a lot of the systems that I test, I don't have a real way to do full end-to-end testing. I don't have a way to set up data nicely, watch it flow through the system, give expected results and get to a final answer, and then clean everything up. It's very piecemeal. That's not necessarily why we got Eggplant. But what I have been able to do with it are a lot of smoke tests, which we didn't have, and several others. There are also some look-up screens where we set up look-up values for other areas, and we have been able to do full testing on those. We have actually found some errors in one application, errors that have gone into the backlog, and we hope to get those fixed so that we can keep building out more tests. It has enabled true end-to-end testing. So far, we've been able to get Eggplant to test anything that we've wanted to test.

Even with the mobile app, which consumes data from a different system, we'll be able to do some full testing within that, which is great.

Our use cases are somewhat unique, because we're not a software development shop. We are testing the pieces that we can and, for that purpose, Eggplant has helped. It has been great.

The model-based test automation has helped to reduce the test maintenance process. Now, I don't have to do a lot of the simple smoke tests and some other testing.

And while I wouldn't say that the solution has helped to uncover critical bugs that normal testing would have completely missed, it certainly has helped us find bugs and then verify that they've been fixed. In one particular instance, it found out that the continuous integration pipeline was broken, or that somebody forgot to push out all of the correct files, because pages weren't working. It pointed out that there was an issue with the deploy model.

What is most valuable?

I have really come to like Eggplant. Although I'm working in QA now, I worked as a dev for a very long time and I like the solution's scripting language, SenseTalk. It's pretty easy to use.

I also like the IDE and the helpers that it gives when you search something and double-click it. It gives you the outline that you can then fill out in your code, which is very similar to many others. I appreciate that they're doing that.

What I'm also really happy about—and perhaps this isn't technically about functional testing, but it's related to it—is that DAI's newest release allows us to test via scripts rather than models, because we have done 95 percent of our development in functional, not through modeling. I am really happy that then we can use the controller to run scripts rather than having to translate things to models. There are lots of options.

We have mobile apps that we are testing through it with Android Gateway, and that seems to be working great. And, of course, any web apps and Windows applications have been no problem. We are running several scrum lines, and we've just implemented with QA and, therefore, QA is important. What we're trying to do is get the ongoing suite of tests that look at things currently, and then it will be a built-on regression suite as we keep going and keep adding more and more tests. We want to improve quality before handing it off to our customers. If we have mainframe stuff, it's nothing that I've had to test or deal with. 

It's been very fast and very easy to use. Because there's that code behind it, we're able to write modularized code, so that when a new page is created, we don't have to rewrite everything, just the things that are specific to those pages.

What needs improvement?

The IDE could be even more full-featured. Because I was a developer, I was very spoiled by either Visual Studio Code or Visual Studio for shortcuts. For example, I was able to say "ctor" and hit Tab and it would create a template of a constructor for me. Or I was able to quickly type out a class mod with properties and methods using prop and hitting Tab. It would set up the template for me. It would be great, when I want to create a new function, if there were shortcut commands like those that help create all of the functions, or if there were shortcut features to do any of the complex plans. 

I would also like to see some of the syntax updated. They have the equivalent of a switch, but it's a very weird IF statement syntax. That could definitely be improved.

Another area that I would like them to improve is their database connectivity and ability within a database. Still, we've been able to use it with what they have and get it working.

For how long have I used the solution?

I have been using Eggplant Digital Automation Intelligence for about 14 months.

What do I think about the stability of the solution?

I can't think of any problems. It's been stable for me.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

We have emailed their tech support and they have been absolutely fine. They have usually responded within a day. If needed, I can jump onto a Microsoft Teams call and work directly with their tech support to get problems solved.

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

Before Eggplant, what we had been doing was C# programming in Visual Studio using Selenium, Gherkin, and Cucumber against Chrome, which is our preferred browser. The reason we went with Eggplant was that we had to use a VM to get to a lot of the products that we use internally, to help test them. The ability to test in virtual machines was huge.

How was the initial setup?

The initial setup was straightforward. It was just a matter of installing the solution locally. It took longer on our side because we had to get a dedicated server, but once we had that server, setting up the license manager on it was very straightforward. Putting in new licenses for it when they expired, until we got our permanent ones, was quite easy. I had no problems with any part of the setup or in running it.

For the third person on the team who's been using it, the biggest issue has been permissions. She's not a developer like the other two are, so she doesn't have local admin permissions. We've just had to go through help desk at times, but otherwise it's been very easy.

Our implementation strategy is that we want to get it up and running and to get scheduled tests and their results. That's what we're working towards. We're hoping to generate some sort of report, whether it's a CSV or something along those lines, to see the daily scheduled test-run results.

What was our ROI?

We're still in the process of setting up ROI metrics. The last number that I saw is that we probably have 200 scripts running. We're trying to get them on a daily schedule, and that is about three hours of testing that we don't have to do, and that's per day. Every day it does the regression testing and we know if we have any problems.

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

In terms of deployment of the solution, we have an internal server in a private cloud running the licensing machine and we have three dev licenses for the product as well as two run-time licenses.

The development license allows you to run Eggplant Digital Automation Intelligence and allows you to test it and run your script. The runtime license is what is used when you set up a schedule. All it needs is a run-time license to run the executables and run the tests. But since you don't need the full Eggplant Digital Automation Intelligence Functional IDE, you just need the run-time license.

Which other solutions did I evaluate?

The other QA in our organization was looking at a testing product called Ranorex. After they fully understood what it was he was trying to do, they're the ones who said that Eggplant is probably the best solution for that.

What other advice do I have?

Jump in and try it. Don't be afraid of it. Before COVID, Eggplant would train a client for two weeks onsite and then everything would be handled through tech support. Not that the worldwide pandemic was good, but because of COVID we started getting a weekly meeting with one of their tech people, and that has been awesome. He's been a great resource. We go through scripts with him, we can send him something and he can respond back via email. But we also have face time where we can say, "Hey, I tried this, it didn't work," and we can sit there and work together through the issue and figure it out.

Utilize all the resources and play around with it. It's not a simple system, but it's worth learning the details of it because you're going to get so much more out of it.

If someone were to say to me, "We are not comfortable with automating 70 percent of our linear path," that would be fine with me, because I'm not trying to sell anything. But I would point out to them that, by having a robust regression suite that they can run and that they can rely on, they are going to free up their testers to be able to work on the edge cases or the strange business issues. They will be available for all of the manual testing that is either too complex or consists of one or two things that just change often enough that they're difficult to automate. It lets their people then focus on those things rather than just the basics of whether or not the code was released properly or files were forgotten.

The team that I'm on mainly works with web pages. I don't actually have to worry about the stuff that we got Eggplant for. It just so happens that I can also use it to test our web pages. We are not a software development company, we're a transportation company. With a lot of the different tools that we have, what our in-house developers have often done is translate data or move data in file form between databases. Sometimes, the front-end web pages, for example, might end up being a report, or they might verify that customer data has gone in, or they verify fuel prices for comparison to what we paid and to see if we can do better.

Eggplant is not worked into our development cycle. It's a tool that I use to automate tests, but it's not something that we've used in a way that would help accelerate the release of a major enterprise-wide upgrade.

We don't use the solution's AI-driven automated exploratory testing. If we let it loose on our website, it would find a lot of dead ends because if data pages are not updated, and they can't upload that, they can't really go any further. Even if they could upload a couple of files, that requires going off to other systems in the background for testing, and some of it doesn't even go back to a main interface directly. That's not to say that maybe someday we wouldn't work in the model area, but at the moment I personally have been more comfortable and happy to work within the functional model.

Being a developer, the solution has reinforced a lot of my development skills. In the context of the programming acronym SOLID, it is still possible to use programming skills and to make sure that you are writing small snippets of reusable code. It has also shown that QA isn't just manual testing anymore. There's a very big automated component and you really do need people who either want to be developers or are able to develop, because that is what is required now. It's what allows you to make better, more robust tests, and things that can either recover or give you good data on how your systems are performing.

Disclosure: IT Central Station 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.
Flag as inappropriate
DH
Senior VP Operations at a media company with 1,001-5,000 employees
Real User
Top 20
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.

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 technical 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: IT Central Station 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.
Flag as inappropriate
Learn what your peers think about Eggplant Digital Automation Intelligence. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
542,721 professionals have used our research since 2012.
DM
Business Analyst at a computer software company with 5,001-10,000 employees
Real User
Improves our software quality by detecting things that the human eye cannot

Pros and Cons

  • "Everything is happening on the layout or display that is used by the user. Eggplant prompts processes, like 'click here,' or 'look for this image.' Eggplant makes it possible for QA people and BAs, working in the actual display, to check if the software is providing the right images, the right text, and the right results. They don't have to go inside the code or to the TCP/IP layer. Everything is happening at the highest level."
  • "I would like to see standardized actions already built into Eggplant. For example, "wait eight seconds". That way, I wouldn't need to create it as an action. Right now, I have to program that wait and describe it as an action so that everybody knows it is an action that waits eight seconds... That way, somebody who is not familiar with programming processes like "if-else", or "for", or "while", would be able, from the first moment, and without programming, to put some easy-to-use, standardized, actions in place."

What is our primary use case?

We provide software for doctors and hospitals. In one of our business units, business analysts and quality assurance people are working together and there is no requirement in the job description for programming. These users are doing the tasks the doctors would do. In the testing environment, they don't need technical, medical knowledge. They are just testing the software in a process that mirrors how a doctor would behave, what a doctor would do for the patient.

How has it helped my organization?

Everything is happening on the layout or display that is used by the user. Eggplant prompts processes, like "click here," or "look for this image." Eggplant makes it possible for QA people and BAs, working in the actual display, to check if the software is providing the right images, the right text, and the right results. They don't have to go inside the code or to the TCP/IP layer. Everything is happening at the highest level. You don't need much coding knowledge to program what can sometimes be complex processes.

Eggplant works very well when it comes to uncovering bugs. In many cases, it has revealed bugs in our tools and modules. That is great.

It has also helped to quickly stabilize updates. It has improved the whole process in acknowledging the images and texts that are shown. Everything is running even better than before.

In addition, it reduces and even eliminates test processes that might have otherwise been necessary for us to do as part of quality assurance. I didn't have to do those processes, Eggplant was doing them. For example, there was a formula used by doctors every day. For a human to check it would take eight hours, but Eggplant does it in two hours and 20 minutes. It's quicker.

We also get better quality because a human eye, after such long and concentrated work, can't see what could be very important images or very rare results. It just doesn't see them anymore, but Eggplant recognizes them. We had an example where a certain text was not Arial 12 but, instead, Arial 9. Human quality assurance people were not able to recognize that, but Eggplant recognized it and told us that something was wrong. We just activated Eggplant and it did the work for us. Eggplant has influenced our release schedules greatly. It showed us errors that we must not have when the doctors are working with our software in real life. It has definitely improved the quality of our software. Eggplant found all the errors before release and gave us the information we needed to look closer at some of our modules, and we improved the quality of our product as a result.

What is most valuable?

The digital twin tool is perfect for combining the non-technical and technical sides. Someone who is not actually in the code can understand the processes that are presented by digital twin. I was introduced to it with a short introduction of about one and a half hours, and I was very surprised to see something like that because I had only been working with Eggplant programming and coding. With digital twin I can program something and visualize it within a module, within a process. For us, an example of such a use case is creating a new patient.

These small use cases are visualized in actions. Everybody who looks at it can understand what is meant by the representation and what an action is doing. In the past, everything was programmed and nobody could understand what I was doing. I put things in modules and described them very clearly, but if somebody was going into the modules, there was code and nobody could understand what it was doing. Now, everybody knows, when clicking on the action, what is going on in the software.

I tell my colleagues, "Look people, when I'm gone, with digital twin, everybody who is working with me will know the actions and can use them and can create a whole process that is visualized, installed, and implemented in Eggplant." We need to understand each other from the first moment, when I'm coding something. That is what is possible with digital twin.

What I like the most in Eggplant Manager is the functionality where you are informed, via email, if something is wrong.

What needs improvement?

For the future, I would like to see standardized actions already built into Eggplant. For example, "wait eight seconds". That way, I wouldn't need to create it as an action. Right now, I have to program that wait and describe it as an action so that everybody knows it is an action that waits eight seconds. Another example would be a "while" process: while this variable is less than 100, for example, do X. That way, somebody who is not familiar with programming processes like "if-else", or "for", or "while", would be able, from the first moment, and without programming, to put some easy-to-use, standardized, actions in place. Eggplant is such a great tool, but everything is based on programming.

It would be nice to have something like Microsoft's automation tool has. That tool has pre-programmed use cases. Everybody who uses it the first time understands what is meant by the "wait" process. Everybody can get in and program. That is not possible right now in Eggplant. If somebody asks me, "Is it possible, from the first moment, that somebody who has never used Eggplant can create actions?" I must answer, "No, it is not possible." Currently, it requires teamwork where somebody programs the actions so somebody else can use them. Eggplant doesn't have standardized actions right now.

Also, the longer the code for a process is, the greater the possibility that Eggplant will not find, for example, the images we need it to find. My advice would be not to program 5,000 lines of code. Try to reduce it to 1,000. Eggplant works very well when it comes to finding the images that are required, but when there are more than 1,000 lines of code, there's a kind of delay in every network. I don't know if this is an Eggplant issue or not, because Eggplant works very intelligently, but eggplant waits for the next action. If a required image can't be found within one millisecond, Eggplant is already responding, "I haven't found anything." Although Eggplant has intelligence built-in, it needs more. The stability would grow if Eggplant did not give up in the first moment and, instead, continued to look for an image a little bit longer. There is a delay in every network environment. It would be great to implement some kind of process in Eggplant that allowed the system to wait longer and to communicate more with the system.

For how long have I used the solution?

We have been using Eggplant Digital Automation for between three and four years.

What do I think about the stability of the solution?

Overall, the stability is good.

What do I think about the scalability of the solution?

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.

How are customer service and support?

There were occasions where I asked questions about coding and, within 15 minutes, I got answers. That was perfect. I wrote to support about every little process that stopped me and got the answer about coding within 15 minutes. Other questions that were a bit more complex needed more time and it took them 24 hours to resolve. Support reacted very quickly. This is a point in favor of Eggplant, one that I want to stress when trying to convince my new business unit to adopt Eggplant. Support reacts so quickly. The kind of communication they provide and their politeness make it perfect.

How would you rate customer service and support?

Positive

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

End-to-end testing isn't possible for us because of the licensing problems. It's very expensive, so we only have two development/execution licenses.

What other advice do I have?

When I started programming in Eggplant, everybody who looked at my screen just saw a lot of code. But when I activated it by pressing play, and that code was working in the background and started doing all the tests that a human would do, everybody said, "Hey, Eggplant is doing it. Cool." Everybody liked it. But the processes behind that, which needed to be programmed, was the part nobody liked.

Right now, I'm totally convinced about Eggplant, and I try to convince others in my company about it. There are some other tools I have to evaluate, and to give my opinion about, but no doubt Eggplant will still be my favorite.

Disclosure: IT Central Station 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.
Flag as inappropriate
DanielWildermuth
Testing Tools Expert at Helvetia Versicherungen
Real User
Top 10
Enables you to insert all the various elements into the repository and then run your tests

Pros and Cons

  • "The most valuable features would be the image recognition and the OCR."
  • "In terms of additional features, it would be helpful to have one package for all testing. You have the manager, the AI, then you have functional, and about 10 different packages for installing."

What is our primary use case?

I'm a Test Tool Expert and we're customers of Eggplant Functional and have a good relationship with them. We were the first company in Switzerland to use them. We automate regression tests and there are eight people in the company currently using the product - some are testers and some developers. On a given day there would two or three people using the product, others might use it once a week or once a month. 

What is most valuable?

The most valuable features would be the image recognition and the OCR. We're also using the API now. we also made a POC for the Selenium WebDriver.

When comparing with other tools, the clear advantage of eggplant is that it is system independent.

What needs improvement?

When you have release branches and you make feature branches then you can commit. But you cannot make a push, that can only be done on the master and it's not very compatible.
It can also be difficult if you write a lot of scripts and have some images. If you change the name of one of the images then you have to figure out where it is in the script which can be difficult. I would say make the possibilities not only on the image recognition but also on text recognition, something which Tosca has. It would be helpful to be able to work with drivers like Selenium. The implementation of the Selenium driver is not very compatible.

In terms of additional features, it would be helpful to have one package for all testing. 
You have the manager, the AI, then you have functional, and about 10 different packages for installing. 

For how long have I used the solution?

I've been using Eggplant Functional for three years.

What do I think about the stability of the solution?

We haven't had any issues with the stability of this solution. 

How are customer service and technical support?

Technical support has really been very good. 

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

We used to use UFT but not anymore, because we have a lot of legacy applications, and we use a lot of different systems that are dependent on each other and because we are independent from where the system hooks up.

How was the initial setup?

The initial setup was very easy. The only thing, which is not so easy is the Eggplant AI integration because it requires an agent to make the connections between functional and the AI server. We had a problem with that but I was able to sort it out. In 99% of cases it works without any issues. 

What about the implementation team?

We had a consultant to assist with implementation and we were very happy with that. 

What other advice do I have?

The product isn't pre-installed. We use xCloud. It really is a very good product, very cool.

I would rate the product a nine out of 10. 

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