Appium vs. OpenText UFT Digital Lab

1. It's open source which supports range of languages, operating systems and languages. Well suited for Android and IOS mobile automation. Supports all kinds of apps, which makes it flexible and robust mobile testing tool 2. It is less appropriate where we need intercept network call to verify the API calls. Extensive coding experience is required to work Appium

Incentivized

UFT mobile works really well if/when you need physical devices under your management. Managing physical devices in any setup is an interesting undertaking due to the various considerations per device. There are really nice best practices, for example using managed USB switches like the one from Cambrionix, that can help make for a really good experience. For us, we only have 1 application at this time that has frequent updates/releases. We are able to test out these with confidence using our suite of real/on-campus devices managed and made available by the UFT Mobile product.

Incentivized

• It uses WebDriver API so it makes it easy to use for former web test automation engineers.
• It can be managed via the command line via an extensive set of parameters.
• It handles implicit waits at the server side that is especially valuable in distributed infrastructure.

Incentivized

• Remote access to real devices within your organization network as compared to public devices library offering, where their is a risk of exposing pre-production builds outside the organization.
• "Factory built like" integration with HP ALM, HP Sprinter, HP UFT and HP Network Virtualization.
• Ability to mimic real world conditions in a controlled environment in the devices of your choice.
• Removed the guess work out of using emulators
• Able to extend automation to mobile testing using HP UFT.

Incentivized

• Element browser sometimes is unreliable and has sporadic fails.
• Appium running is a bit slow, compared to tests written with Appium and with Espresso or XCTest.

Incentivized

• Most of our problems are with the lengthy onboarding process with iOS devices.
• Occasionally Android devices will disconnect themselves.

Incentivized

The tool continues to meet our expectations and has shown that they are continually evolving the product with new features that benefit us. The most recent new feature was the auto-signing/packaging of iOS apps from the server to allow native interaction of features like biometrics. Prior this was a lengthy exercise.

Incentivized

If you're an Apple developer, you use Xcode. It's practically a forced necessity. For system testing though, it doesn't have to be. You can have your development team focus on unit and integration tests in their platform and another team automate acceptance tests with a language they are more familiar with.

Incentivized

HP Mobile Center stacks well against solutions like Mobile Labs Device Connect, Perfecto Mobile and Device Anywhere. Its native integration with HP ALM and HP UFT makes it a clear choice for team already using those solutions. HP Mobile Center also provides extension to Amazon Device Library.

Incentivized

• Appium is open source, so it's free. That's budget friendly right there.
• The ability to write mobile automation tests has saved considerable time for our manual test team, but that is true with most automation tests.
• We use Sauce Labs with our other automation, but Appium works great with Sauce Labs, as well, if I needed to run on emulators and simulators.

Incentivized

• Efficient use of the devices. Reduced the idle time.
• Better control over access and user management. Testing within our controlled environments.
• Better control of device matrix.
• Faster testing cycles. Early design bugs to development teams. Real devices means, less guess work.

Incentivized