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.
Integration Specialist at a financial services firm with 10,001+ employees
Real User
Top 5
Aug 19, 2019
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.
Test lead/Senior Mobile Automation QA at a non-tech company with 51-200 employees
Real User
Jul 31, 2019
We found that we had issues regarding the VPN setup, which is one of the reasons that we did not purchase this solution. We found that the interface is not user-friendly. We were not able to write code as fast as with the competing open-source software, so that needs to be improved. We were not able to view all of the resources that were present.
Teamleader Test Software at a healthcare company with 501-1,000 employees
Real User
Jul 1, 2018
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.
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...
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.
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.
We found that we had issues regarding the VPN setup, which is one of the reasons that we did not purchase this solution. We found that the interface is not user-friendly. We were not able to write code as fast as with the competing open-source software, so that needs to be improved. We were not able to view all of the resources that were present.
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.