- Jun 07, 2018
- admin
- 0
Challenges using APPIUM
- Setting-up and Scaling-up – Appium, is only installed locally. That makes using it in a highly-secured Enterprise environment almost impossible. Testers must work with IT teams to get the correct machines, permissions, access and administrative rights. Appium is also hampered by its inability to work across different operating systems. Enterprises need to be able to test on every possible configuration of an app and OS. In order to do that, they need to test with a huge matrix of devices. Appium can only connect to one device at a time per machine. This makes scaling up to include more devices prohibitively difficult.
- Test Development – Enterprise app testers require the capability to identify elements and control them within their applications. This means that applications need to work, and also need to interact correctly with the device itself. An application that uses microphone, camera, or NFC chip must have that connection tested. Appium testers in this position end up spending massive amounts of time finding workarounds which lead to major delays when application testing.
- Test Management – As mobile testing project scale, testers require accurate reporting software. Appium is problematic because users need to spend a lot of time connecting Appium’s software to third-party reporting systems. Another necessity is having the ability to automate tests that will extend beyond one device, and operate on dozens, if not hundreds of devices. Testers that use Appium must set up a grid of devices and machines in order to execute their tests. This makes application lifecycle management (ALM) extremely difficult.