I downloaded and set up Appium to run tests for an app developed in ActionScript for the iPad. I can run Appium just fine, however am having trouble actually writing tests. The problem is that I don't have any way to retrieve elements from the app. I thought I could do this with the selenium driver (I am currently creating an IOSDriver with Appium), however can't seem to figure out exactly how. All of the elements created by my application are flash-based (TextField for example), so I'm not sure how to retrieve them with the normal findElement method(s).
(Note I cannot update the code to comply with my tests, it must be the tests that comply with the pre-written code)
The Accessibility-based mechanism underlying the UI Automation feature represents every control in your app as a uniquely identifiable element. To perform an action on an element in your app, you explicitly identify that element in terms of the app’s element hierarchy.
This link is useful Tutorial
Tools You may like to try Although they are not exactly like UiAutomatorViewer which is for android
Reveal App
SparkInspector
Ios Hierarchy-Viewer
As far as Flas Elements concers Lets Look at this tutorial.
Related
While running automated test using appium I used driver.getPageSource() and stored it as a XML file. I also took the screenshot of the same page using driver.takeScreenshot() and saved it as a PNG file. Now how do I view it in Appium app so that it correspondingly maps to the elements with the xml data.
Is there a open option in Appium like in uiautomatorviewer?
I couldn't use uiautomator because it requires uix file. But I couldn't find open option in appium.
UIAutomatorviewer is simple tool to start with mobile automation , however it has some limitations
Less robust:
Throws random errors while working with native apps
Limited functionality:
Limited features as compared to APPIUM Desktop
These limitations do not allow UIAUTOMATORVIEWER to be a universal choice among the automation engineers , and mostly it’s used along with Appium Desktop.
For Installation and Usage you can refer below URL
https://automationlab0000.wordpress.com/2018/12/31/appium-desktop-for-locating-elements/
Due to the complex setup of Appium, it is quite difficult to be dependant only on Appium for mobile automation.
With Appium Studio of SeeTest you can easily identify objects.
Appium Studio mitigates all of Appium's challenges with ease. There is also an object spy for easier object and XPath identification. Tests are recorded simply. Actions carried out on the device reflection are recorded in an easily exported and executable test written in the language of your choice.
Visit this blog for more details.
Refer their docs to get started https://docs.experitest.com/display/public/TD/Appium+Studio
We are trying to automate an android screen in which there is a progress bar which gets updated every second. Our framework retrieves the UI dump using adb shell uiautomator dump to get the UI heirarchy layout and then parses the xml to take further actions. We observed that for the above mentioned screen we are not able to get the dump and the above command reports an error "Could not get idle state".
On the same screen, we tried with appium and appium is able to retrieve the elements on UI. How is appium able to retrieve the information, which UI Automator is not able to retrieve.? We would not want to integrate appium as a tool at this point in our framework and would like to use ui automator dump itself. Is there a way to overcome this issue?
The thing is that Appium has 2 drivers for Android: AndroidDriver and UIAutomator2Driver (for Android 5+)
The 2nd one is a custom client-server implementation of UIAutomator:
https://github.com/appium/appium-uiautomator2-server
https://github.com/appium/appium-uiautomator2-driver
So it literally means "Appium don't use UIAutomator as is" any longer.
Google is no longer supporting UIAutomator (last release was july 2017) in favour of Espresso.
Check code of server part and you will understand that with UIAutomator2 Appium overrides lots of original UIAutomator stuff to solve issues like you described and many more.
If you don't want to use Appium, you still can reuse UIAutomator2 Server or at least write your custom framework on its basis and solve issues of original UiAutomator.
I see on Android that apps exist to create android apps. I understand nothing like this exists on IOS because of apple's terms. On IOS however, some apps, pythonista for example, allow the user to create scripts that run similar to apps. Is this functionality currently available for hybrid frameworks, IE phonegap/cordova, react native, etc? Barring this, is there some method whereby I can code and test such apps on my iPhone/iPad?
Bottom line, I want to code apps while commuting, etc, on IOS. I understand I need a computer to compile the final product, that's ok, it's just the coding/testing process I want to do on IOS.
I am up for any hack you can think of to make this work, so long as it is accessible with VoiceOver, apple's screen reader, as I cannot see at all. One example of something I thought of that won't work is using remote desktop software, there is no such software that is accessible as it uses an image of the remote screen, I have no access to this.
I am looking forward to your creativity, so far this has me stumped.
Thanks in advance.
Similar to the playgrounds answer, but if you wanted to use Xamarin you could use Continuous .NET. It’s a C# IDE for iOS. You could then use Working Copy to to keep the version on your computer in line.
The other option is to VNC into your computer at home, but if you’re on the train that might not be a great option.
It's not a solution for your problem, but if you have an iPad, you can write parts of apps in Swift Playgrounds. There you have access to all the UIKit stuff. Unfortunately some of the frameworks you can use in iOS are missing.
I have used Appium in Mobile automation with IOS and Android. I wanted to know about advantages that offers Calabash and if there are common point in generated scripts of both tools?
I have followed this link : Appium VS Calabash
I have hands on in mobile automation quite a long time. let me tell my point of view on both tools.
both also have advantage and disadvantage find below:
I have used calabash and appium both for automation. Appium has more advantages than calabash.
Advantages of Appium over Calabash:
1. You can write your code in multiple language like Java,Python, C#, php etc. However, Calabash restrict to use RUBY only.
Appium comes with many predefined methods such as OpenNotification(), StartActivity(), InstallApp etc. Calabash does not provide such predefined methods.
Appium set up is very easy as compared to Calabash.
In calabash, it installs the app on the device every time you run the test. However, In appium you have a feature where in you don't need to install the app every time. It works with previously installed app on the device.
Appium works with both native and hybrid app.
There are many advantages of appium. I hope this helps.
Try them both for yourself.
I found calabash easier to get started. I had a complete user flow test working from setup to working test in Calabash in half the time it took for Appium.
I don't like using xpath. It makes tests brittle and subject to breakage if something in the layout changes. Appium requires mainly the use of xpath. Calabash allows you to drive actions and interactions through the selection of elements by their text . I prefer this because that same text is normally in the designs and/or requirements.
Some comments in other posts are not accurate. Calabash does not require the install of the app every time unless you don't look beyond the surface. There is a simple means to enable/disable it. I have logic that runs either way based on passing an argument. Calabash has more than enough existing methods to interact with your app. It has a built in debug that allows you to tinker with element interaction and those same calls can be copied and reused in your test code. Using it with getgauge.io provides reporting akin to the built in Cucumber but is easier to run multi-threaded and easier to write your feature/spec files.
Be fair to both tools and yourself. Create a simple project in each and try for yourself. Don't make a decision solely based on someone else's opinion.
There is no common part in the automation scripts since Calabash uses query for interacting elements but Appium uses selenium find functions.
The best part of the Calabash is that you can use cross-platform frameworks for automating ios and android application with same feature file and most part of automation code. However the worst part is that Calabash is Ruby only.
Look at this post for more details about the differences of Calabash and Appium.
Since you have already read the differnces , Few things to note that Calabash can also be used with Xamarin which is also a good tool to test hybrid apps and you can run the same script for ios and android apps with some minor changes.Also it has been now integrated into visual studio,so microsoft support is inevitable and some users might feel comfort factor.Lambda expressions are also a plus.A major setback with the Calabash however that it only uses ruby.
Appium on the other hand can support various languages which is plus and you can use webdriver as well.However it struggles with hybrid apps but you can overcome that functionality by using google chrome mobile view to find coordinates to click.one thing for sure is that sause labs have many bugs to fix in Appium yet.
I need to know if I can do Continuous Integration with XCode server. In example: set run the tests every night or when someone commit changes, and more..
I am trying to decide one iOS Ui Automation tool to integrate with my Xcode server
Thanks
There are a few problems here:
UIAutomation has no built in support in Xcode Server. I've filed bugs, I've chased down people at WWDC. Most I've ever gotten on this problem is basically "shrug." I'm not sure UIAutomation is a priority for Apple right now. So you're not going to get any official support.
As was noted, you might be able to use a trigger. The trigger won't be able to add anything to the Xcode Server report, besides possibly the error logging. But you're not going to get anything added to the nice report table.
Running on actual devices has traditionally been a problem (if you care about that.) The loading the app part has been a problem for us, but Xcode Server might be able to preload the app for you. In addition, it seems like this might have changed in the iOS 8 SDK.
There is just a lot of uncertainty around this sort of workflow. I'm hoping Apple eventually makes an announcement or adds a new tool, but the best answer I've gotten is if you want to go down this path, use UI Unit Tests. That's a shame because it requires knowledge of Obj-C or Swift, and means interacting with the app at an API level instead of an abstract level, but if you're looking for the direction Apple wants to see people go, that's it.
Edit 7/4/2015: As of WWDC 2015, there is a new UI Testing component as part of Xcode 7 that, in my experience, seems totally supported, and is promising Xcode Server support. I would very strongly recommend using that, and not using the Instruments UIAutomation tool.
With Xcode6 right around the corner they are adding some features to XCode Server specifically it looks like "Triggers" will be helpful for running iOS UIAutomation tools. Since you can run UI automation scripts from cmd line it should be possible to utilize triggers to run your scripts post builds. This along side the logic for when a bot should run will let you decide if it should be nightly or on every commit.
https://developer.apple.com/library/prerelease/ios/documentation/DeveloperTools/Conceptual/WhatsNewXcode/Articles/xcode_6_0.html#//apple_ref/doc/uid/TP40014509-SW1
I wrote a framework around UIAutomation called Illuminator to handle tasks like nightly test runs, pull request tests, and other automated conveniences.
It provides a flexible and extensible command line that can execute any particular subset of tests that you'd like, and produces reports in JUnit format (used by Jenkins).