Explain the difference between iOS and Android in testing




Only by understanding the different design concepts of iOS and Android operating systems can we design test cases better and test apps more comprehensively. Fragmentation of

Android App Testing Devices For the iOS operating system, the App only needs to support limited devices and resolutions, and there is no need to worry about the impact of device fragmentation on the App when testing the App on Android.

Google adopts an open strategy, so many manufacturers will customize Android, which makes the devices using the Android operating system overwhelming, and the fragmentation of Android is also very serious.

Android apps are more vulnerable to malware attacks. Under the

open strategy, the probability of cracking the app's apk installation files is higher than that of iOS, so it is more necessary to ensure the security of the app.

iOS and Android handle communication between apps differently. The

iOS operating system imposes restrictions on the operating mechanism of the app. In most cases, the app will enter the suspend or terminate state immediately after entering the background, which means that the code cannot be executed; iOS There is no concept similar to Service in Android, but there are some exceptions.

Some important tasks, such as saving user data, downloading from the network, etc., can apply for a limited period of background running time, the length is about 600s, so the operations that can be performed in a short period of time are very limited.

Certain types of apps can run in the background without time limit, including music playback, audio recording, positioning/navigation, VoIP, downloading, and regular updates.

Apple provides the App Calling Protocol URL Schema within iOS to handle it.

Android and iOS are different in whether they support extended storage.
iOS and Android implement and use Widgets differently.
Test Android App compatibility with Dalvik and ART runtime environment (RunTime)
Test iOS App behavior under certain settings

For iOS App, before the advent of iOS 8, Apple's product upgrades will take into account the resolution on different devices Inconsistent, but with the launch of iOS 8 and iPhone 6 and 6Plus, the zoom display function on iPhone 6 and 6Plus will make the App display different in standard display and zoom display modes, so testers need to Test the display effect in these two modes.

The memory management mechanism of the iOS operating system and the restrictions on the memory used by the App are very opaque.

Since there is no real multitasking and no swap mechanism on the iOS operating system, the iOS operating system will first warn the App of memory usage when the memory is insufficient. If the App continues to consume memory up to the maximum allowed by the iOS operating system, iOS will directly "kill" the App process.

Testers can use the device with the smallest total memory of the iOS device supported by the app, use Xcode to check whether the app's memory usage exceeds the limit, minimize the app's unnecessary use of memory, and check whether the app has memory leaks by the way.

The memory management mechanism of the Android operating system is more transparent, and the restrictions on the memory used by apps are more flexible.
On different Android devices, the amount of memory that each app can use is different. Testers can open the /system/build.prop file to Check the maximum available Dalvik memory size for the app.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326219678&siteId=291194637