We performed a comparison between Appium and Tricentis NeoLoad based on real PeerSpot user reviews.
Find out what your peers are saying about OutSystems, Mendix, Salesforce and others in Mobile Development Platforms."The solution is easy to use."
"It's an open-source solution with a very large community and available documentation."
"Appium has easy interaction with mobile."
"The most valuable feature is that it's easy to launch applications. Appium has everything that Selenium has. So many good tools support Appium. We can take some Excel sheets and use them to fill out the text box that's in there. We can also take screenshots of failures."
"It has great documentation and excellent community support."
"Appium provides a record-and-play option, and the commands are the same as those that Selenium uses. So a person who has some exposure to Selenium will be able to write a piece of code in Appium."
"The most valuable features of Appium are the in-built functionality, which we can use in our code. For example, move back, move front, navigate one page before, and navigate one page ahead. You can do this by using the in-built functions from Appium."
"The library is extensive so the driver interacts with most functions or actions on mobile devices."
"The Frameworks feature is valuable. NeoLoad Web and the API are also valuable. It provides API support."
"The most valuable feature is the ability to execute parallel requests, unlike JMeter and LoadRunner which can only be run sequentially."
"In my opinion, correlation of dynamic data is the most important advantage of this tool."
"Tool for load testing and performance testing with good API support and good technical support. Tricentis NeoLoad is absolutely stable and scalable."
"The most valuable feature is flexibility, as it connects to all of the endpoints that we need it to."
"Very easy to use the front end and the UI is very good."
"I would rate it as eight out of 10 for ease of setting up."
"NeoLoad is actually really good, mainly because they have a world-class support service."
"Image recognition could be improved. We have some images in our mobile applications. It should be able to run from the cloud, so we can automate the catcher."
"It needs to accommodate applications that use React.js and AngularJS."
"The setup and installation were a problem for us at first."
"What needs improvement in Appium is its documentation. It needs to give more context on the libraries that Appium is using under the hood. For example, my team is using Appium for Android automation, and a lot of times, I feel that there's functionality that's available through the Appium interface, that exists within the UIAutomator, but there aren't a lot of useful or helpful resources on the internet to find that information, so it would be good to have some linkage with the underlying platform itself. Another room for improvement in Appium is that it's buggy sometimes. For example, at times, there's a bug in the inspector application that doesn't allow me to save my desired capability set, so it would be nice to get that bug fixed, but overall, Appium is a good tool. The Touch Actions functionality in Appium also needs improvement. For example, if I want to initiate a scroll on the device that I'm running Appium on, sometimes Swipe works, but in other situations, I have to explicitly use action chains, so I'm not too sure what's the better approach. What I'd like to see in the next version of Appium is a more intelligent and more intuitive AppiumLibrary, in terms of identifying menus and scroll bars, etc., because right now, I'm unsure if I have to do a lot of export reversals to get to the elements I'm looking for. It would be nice to have some functionality built in, which would allow me to easily get those exports."
"If it had more facility for configuration it would be a spectacular solution."
"Stability is an area that needs some improvement."
"I rarely use Appium nowadays because I'm now at the managerial level, but the last time I used it, whenever I selected and clicked on an element, Appium was very slow. I tried to debug it, but I still couldn't find the problem, so this is an area for improvement in the solution. Another area for improvement lies with the connector and server. For example, the effort to get into the local machine sometimes causes the emulator to become slow, which then leads to failure in testing, and this is the usual issue I've encountered from Appium. An additional feature I'd like added to Appium in its next release is being able to do automation in iOS without using XPath and the name of the element. In Xcode, you can use previous UI tests for detecting elements, but in Appium, you have to use Xpath and the element name instead of being able to directly put the X-UiPath, which is what you can do in Xcode. In iOS as well, sometimes the element doesn't have a name or a path. Sometimes, there's also no element."
"Appium could improve by enabling record and run techniques similar to what they have in other licensing tools, such as Micro Focus. We have to all write the code, and then we can proceed."
"Most people focus on HTTPS or TCP, but it would be good to have support for a variety of different protocols."
"Tricentis NeoLoad crashes if an application contains more than 1,000 scripts."
"An area for improvement in Tricentis NeoLoad is its price, as it has a hefty price tag."
"The product must improve the features that allow integration with CI/CD pipelines."
"An area for improvement in Tricentis NeoLoad is its integration with third-party tools because, at the moment, it's a bit complicated. Per Tricentis, you can integrate Tricentis NeoLoad with different monitoring tools such as Dynatrace and New Relic, but that requires installing an additional tool to make that integration happen, rather than being able to pull in Tricentis NeoLoad from the different tools and servers, and make integration simpler and easier."
"It would be good to make some updates on the reporting side."
"Sometimes it's complicated to maintain the test cases. It's much easier than in JMeter, however. I'm not sure if this depends so much on NeoLoad, or is more based on the environment that we are testing."
"Connecting with the solution's technical support can be time-consuming. The turnaround time for a ticket raised is around 72 hours, which becomes an issue when working on a huge project in our company."
Appium is ranked 7th in Mobile Development Platforms with 25 reviews while Tricentis NeoLoad is ranked 3rd in Performance Testing Tools with 57 reviews. Appium is rated 8.0, while Tricentis NeoLoad is rated 8.2. The top reviewer of Appium writes "It's easy to launch applications". On the other hand, the top reviewer of Tricentis NeoLoad writes "Supports SAP and non-SAP applications and helps identify performance issues before production deployment". Appium is most compared with Tricentis Tosca, Katalon Studio, Perfecto, Xamarin Platform and SmartBear TestComplete, whereas Tricentis NeoLoad is most compared with Apache JMeter, OpenText LoadRunner Professional, OpenText LoadRunner Cloud, Tricentis Tosca and BlazeMeter.
We monitor all Mobile Development Platforms reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
