I would prefer more UFT because it has VB scripting capabilities. While Eggplant Test also has this feature, it's not very user-friendly. I prefer the features of UFT compared to Eggplant Test. When needing to do quick automation, I would prefer Eggplant Test, but otherwise, I would always choose UFT. It depends on the complexity of the tasks. For big problems and complex automation tasks, I would prefer UFT because it has more flexibility and is more effective. With Eggplant Test, if you have very low complexity automation, such as simple click sequences and validation, then it would be preferable; with more complexity, I would not recommend Eggplant Test.
The execution times are a little slower, and the two-system architecture that we currently follow could be better replaced with a one-system architecture.
There is room for improvement in terms of the availability of resources in India. Since there are very few customers in the Indian region, there is no training available, and it's challenging to find skilled talent. Also, performance can be slow when executing larger regression packs in a distributed environment.
There was no free trial in it. So, I studied it through a page that tells how it works. It will be good if a free trial is provided for users. Moreover, I would like to give some feedback on the installation process. There are other tools that are much easier to install and get started with. Eggplant could improve its installation process.
Integration Specialist at a financial services firm with 10,001+ employees
Real User
Top 5
Aug 2, 2023
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.
QA Engineer at a computer software company with 1,001-5,000 employees
Real User
Oct 26, 2022
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.
Business Analyst at a computer software company with 5,001-10,000 employees
Real User
Oct 6, 2021
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.
Automation Software Development Analyst 3 at a aerospace/defense firm with 10,001+ employees
Real User
Aug 12, 2021
In terms of what could be improved, I would love to be able to take the font of the application that the team is working in and upload it or import it into Eggplant Functional, so that the OCR is more accurate when it comes to that type of font. Because sometimes when you get into legacy applications where the fonts get a little wonky, they look really old, so a 1 could get mistaken for just an L. So I would love to have that part where it could read fonts that you import into it a lot easier for the OCR. Additionally, there is some stuff around images they need to tighten up. Sometimes it has a hard time finding fuzzy images. I couldn't really tell you what they need to brush up on with the images. But for the most part, it's on point. I would like the company to have a dummy desktop application that they could send or download from the site that you could run Functional against. One of the biggest hurdles we had to go over was when we got Functional and installed it - what do we use it against? We did not really have an application. So we had to just write automation against the calculator or write automation against Notepad or Microsoft Excel. It was kind of lost on some people. They would say, "Well, this is stupid. I actually want to see this being utilized against something that looks like an application." So I wish the company would come up with a dummy desktop application, something that doesn't require admin privileges. Just a little lightweight MSI file or RPM that you could put onto the machine that just has weird dropdowns or windows or buttons that you can click on just to test stuff against them. Something like that would be good.
Senior Technical Support Analyst at Kaeppel Consulting, LLC
Real User
Aug 10, 2021
The biggest issue I had was the crashing. You could be in the middle of setting up and writing up a nice little script and then it would crash. It was a common occurrence and frustrating but we handled it.
Senior VP Operations at a media company with 1,001-5,000 employees
Real User
Aug 5, 2021
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.
Eggplant Test stands out with its AI-driven and image recognition features, facilitating quick bug detection across multiple systems. Its ease of use, coupled with robust integration capabilities, makes it a top choice for efficient and comprehensive testing solutions.Offering OCR, image recognition, and extensive AI capabilities, Eggplant Test enhances automation and reduces testing time. Known for its versatility, it operates independently from system constraints and supports scriptless...
I would prefer more UFT because it has VB scripting capabilities. While Eggplant Test also has this feature, it's not very user-friendly. I prefer the features of UFT compared to Eggplant Test. When needing to do quick automation, I would prefer Eggplant Test, but otherwise, I would always choose UFT. It depends on the complexity of the tasks. For big problems and complex automation tasks, I would prefer UFT because it has more flexibility and is more effective. With Eggplant Test, if you have very low complexity automation, such as simple click sequences and validation, then it would be preferable; with more complexity, I would not recommend Eggplant Test.
The execution times are a little slower, and the two-system architecture that we currently follow could be better replaced with a one-system architecture.
There is room for improvement in terms of the availability of resources in India. Since there are very few customers in the Indian region, there is no training available, and it's challenging to find skilled talent. Also, performance can be slow when executing larger regression packs in a distributed environment.
There was no free trial in it. So, I studied it through a page that tells how it works. It will be good if a free trial is provided for users. Moreover, I would like to give some feedback on the installation process. There are other tools that are much easier to install and get started with. Eggplant could improve its installation process.
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.
Eggplant Digital Automation Intelligence could improve by lowering the price.
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.
Its performance and stability could be better.
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.
In terms of what could be improved, I would love to be able to take the font of the application that the team is working in and upload it or import it into Eggplant Functional, so that the OCR is more accurate when it comes to that type of font. Because sometimes when you get into legacy applications where the fonts get a little wonky, they look really old, so a 1 could get mistaken for just an L. So I would love to have that part where it could read fonts that you import into it a lot easier for the OCR. Additionally, there is some stuff around images they need to tighten up. Sometimes it has a hard time finding fuzzy images. I couldn't really tell you what they need to brush up on with the images. But for the most part, it's on point. I would like the company to have a dummy desktop application that they could send or download from the site that you could run Functional against. One of the biggest hurdles we had to go over was when we got Functional and installed it - what do we use it against? We did not really have an application. So we had to just write automation against the calculator or write automation against Notepad or Microsoft Excel. It was kind of lost on some people. They would say, "Well, this is stupid. I actually want to see this being utilized against something that looks like an application." So I wish the company would come up with a dummy desktop application, something that doesn't require admin privileges. Just a little lightweight MSI file or RPM that you could put onto the machine that just has weird dropdowns or windows or buttons that you can click on just to test stuff against them. Something like that would be good.
The biggest issue I had was the crashing. You could be in the middle of setting up and writing up a nice little script and then it would crash. It was a common occurrence and frustrating but we handled it.
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.