I am using Appium v1.7.2 w/ XCUITest and Xcode v9.2 on Mac Sierra. The automation is being run on a physical iPhone 6. Test cases are executed very slowly and take a tremendous amount time to find elements and perform actions as compared to Android.
Is there any way iOS automation can be made faster?
Related
I want to get into app development for the apple ecosystem and since my current laptop is arriving at his end of life i tough" "What better occasion to get a mac?".
I think I've basically cleared all my points for support on the m1 chip but i was hunted by this doubt: "Are app developed under M1 chip, somehow compatible with the Intel based mac? If not do I have to recompile the code on a Intel based mac?"
Yes, using Xcode 12, you can create universal binaries that run both on M1 and x86. These Apple Developer documents go into the details:
Building a Universal macOS Binary
and
Porting Your macOS Apps to Apple Silicon
(while the second document is instructing about going the other direction, it's still a good reference on the universal binary concept.)
I'm developer working on windows computer. I will start my first Xamarin.Forms project using Visual Studio 2017 on my windows PC. Since the target platform are IPhones, I'll need a new Mac solely as a Xamarin build agent. I never had a Mac before...
Will a 128 GB SSD have enough space to host the essential tools like the build agent, XCode and perhaps Visual Studio for Mac (if I decide to switch later on)?
I intend to keep my Windows computer for all other work, so the Mac is just for building and running the simulator.
In your experience, will 8 GB of RAM be enough - or will it slow down the build time considerably (it's a small project, perhaps 4-8 weeks of work, 1 person).
It is ok as you have mentioned it is a small project for 3-4 weeks of duration. It would be better if you buy 256 GB SSD. Also another idea would be buying Mac mini. Mac mini is a device, in which you can get good configuration for better rate. You can connect Mac mini to any LED monitor and you can work. you can find more details about it here
I'm not sure whether this is the right place for my question. If not, please close the thread.
I'm new to Xamarin.Forms/Mobile development. (not to .NET development in general).
Anyway, when I deploy my very basic sandbox/test app which uses Xamarin Prism (currently only 2 Views and ViewModels) to the Android Emulator, it takes about 2-3 minutes to start the app. I'm working on an Lenovo X1 Yoga (2nd GEN), with a Core i7 7300U, 8GB RAM and SSD. So I can't imagine the specs are to low. I also enabled virtualization in the BIOS.
Is the time it takes to deploy really that long?
I can't imagine how this will go once the application grows?
Is there sometihng I can try t improve the performance, or is this behaviour normal?
Kind Regards
Gilles
We have a peculiar problem if anyone has run into anything similar. We have a fairly large mobile app, built with Apache Flex 4.10 and Air 3.8. Runs beautifully on iOS. Screens are quick to load, scrolling is smooth and the app is almost desktop like. However, on an Android device, it runs painfully slow. Same codebase, both modern devices, everything same. It takes about 4 times as long to run on android as on an iOS device. Any ideas?
The issue turns out is specific to Galaxy Tab 3 10.1. Same app runs significantly faster on a much older beat up Samsung Galaxy Note 2.
Other folks are running into the same issue. (http://forums.adobe.com/message/5773513) . This device ships with an Intel based chip. Air is not supported on Intel x86 based Androids (atleast from their tech specs) http://www.adobe.com/products/air/tech-specs.html
===============
Android
ARMv7 processor with vector FPU, minimum 550MHz, OpenGL ES 2.0, H.264 and AAC HW decoders
Android™ 2.3 and above
256MB of RAM
===============
Really not sure what other folks are doing to combat this, The galaxy tab is probably going to be among the most popular Android devices this holiday season. Does anyone have a similar experience?
When an AIR app is exported to iOS, it is compiled to native code. The Android version is compiled to the AVM bytecodes and is interpreted. This is probably the difference in performance.
I know there have been some requests to compile AIR apps to native Android code, no idea what plans are in place for this.
I was wondering if the iOS Simulator can some how actually simulate the processor speeds of the iPhone 5, iPad 4(retina) and iPad 3 found at this link:http://browser.primatelabs.com/ios-benchmarks
For example if I run an app I create in xcode on the iPad 3 will it run twice as fast on the iPad 4?
This isn't possible. The iOS simulator doesn't even use the same architecture (it's compiled for the Intel chipset as opposed to ARM), hence you can't (at least in the current incarnation) do this.
On a similar basis, the performance information within Instruments is only meaningful when run on a device.
no, it only simulates on the OS, it actually did not check the limitation of processor and RAM