Automation Anywhere vs TestComplete

• Exception handling is pretty decent. WE don't have to worry about process being stuck as it moves to the next iteration on its own.
• Automation is easier to achieve as it doesn't require high coding skills or designing a specific framework.
• It can achieve PDF editing and automation, which in our case of policy documents has been valuable.

Read full review

• The record and play back works great for our less technical team members. Basic UI validations and some of the happy path functionality can easily be automated.
• The structure and set up of Project Suites. Easy to organize tests and group into functional tests that can be reused in Test cases.
• Multiple Types of tests projects can be created. Mobile, Web Page and Web Services. When setting up a new project the wizard guides the user through and allows for the selection of many different options as well as the coding language that is preferred.

Read full review

• Automation Anywhere doesn't come with easy installation, We need to install Java, IDEs and Databases in an orderly fashion which we are not able to do.
• Automation Anywhere has no workflow design which is not making us to understand the process.
• Automation Anywhere has no fit to size object cloning.

Read full review

• Having never used anything like TestComplete before joining my company, it wasn't exactly the easiest application to pick up. The code examples online (particularly the SQL ones) were a little difficult to get the hang of. I was greatly helped by having a guy on my team who had worked with TestComplete for a few years, but the onboarding was a little rough.
• We've run into various errors over the years involving memory leaks (which required a hotfix patch) and even scripts written in TestComplete not running in TestExecute. While these have always been addressed by patches (or new major versions in the case of the TestExecute issues), it has occasionally required some clever work-around in order to get it to do what we need.
• We have encountered many issues running TestComplete in an RDP session to a virtual machine. The RDP window needs to be open at all times and cannot be minimized. This may be a technological limitation, but it would be really convenient if we could run 'headless' scripts as scheduled tasks.

Read full review

• Our overall business has saved numerous hours of work where individuals were freed up to perform higher level thinking tasks.
• Following a necessary reduction in workforce that was not driven by RPA, we were able to automate processes that kept the remaining workload from overwhelming the remaining workforce.
• The use of robotics process automation has inspired many workers to come up with different approaches to problems including both automation and analytics.

Read full review

• We have seen a much more efficient product release cycle since using TestComplete. )Mainly down to the fact that a new build can be issued and tested very quickly. In turn, this means problems can be found a lot quicker, and the process repeats.)

Read full review