I have used Mable, Applitools, and Parasoft. I have used them for web testing.

In terms of Eggplant Manager, I do and I don't have experience with it. I have never used it but I know how to use it. I know what it is. But a lot of the teams at my company utilized Manager in a different way. They utilize a manager type of Eggplant in a different way. They use Jenkins to do the backend stuff, like the overnight running of tests. Manager schedules my tests to run at this time of night against an application. I've told them the sophomore teams I've been on about Manager and they say they already have a tool that does that and they can just run it from Jenkins. So really, the only part of Eggplant that I've ever really used is Functional, but I am aware of how DIA and Manager work. It would be cool to have those tools for a team that doesn't have Jenkins set up to see how they would want to use it, if they're really limited. It is a nice tool, but you're going to end up paying for it.

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.

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.

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. 

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.

We did not have a previous solution.

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.

We did not use another solution prior to this one.