When it comes to mobile automation, the first thing comes to the mind is, “Can we do it for Free”? The answer is, may be. The answer to “may be” comes to Appium, a popular tool. However, is it really free?
Testing of secured, pre-production application with something that you can’t see which has been uploaded in public clouds. Not a great idea.
With SIGOS Appexperience, you have the answer. Your applications are secured in your own account, accessible only by your users, that you can modify, delete anytime you want.
Even with scripting itself, Appium requires a lot of coding. Not to mention it has its limitations.
For example, check out a very common application that is being installed by 10,000,000+ Android users. Consider a very simple scenario, Launch Application, Click Watch Live and verify that it launches the player. Looks pretty simple!
But, when I try to write the script using Appium desktop (to see what objects we can use), I came across an issue even on this simple scenario. Because, on a specific screen, it could not obtain the screenshot, and thus, I have no idea on how to verify (unless I know each and every object in App source).
On the other hand, using Appex Studio and Object command, I can see what is there on the screen.
The best part is that the scripting itself is visual: simple drag and drop.
(Tip: If you are a hardcore JAVA developer and like to code, try the JAVA API)
Along with Object recognition, with SIGOS Appex proprietary commands (Image, text based), you can go one more level deep and verify: “It not just works, but it works perfectly”.
Consider another scenario. Let's suppose that you are writing a script for your shopping applications. The test case is to find a shoe, find the right size and add it to your cart. Check out the image below.
As you can notice, there are two types of boxes where the sizes are provided. The available sizes are within a solid lined box whereas the ones not available is greyed out. If you look at the left side of the screen, the way device’s accessibilities API works, it cannot differentiate between the two, at least in this case. So now we are stuck.
Oh, did I mention monitoring of the application(s) using the same script created for testing?
You can place some timers around the verifications in your script, measure the real user experience time in milliseconds, create reports, have some alarms placed for your NOC team along with escalations to management, all in the same tool and UI.
In summary, here are some key advantages for mobile application testing and monitoring for iOS and Android devices.
Start Monitoring today. Get your free Trial with SIGOS.