In the technical exchange group I created a few days ago, several students chatted about topics related to compatibility testing. There are testing methods and skills, how to choose the entry point for testing, and how to balance quality and input cost.
After looking through the rewritten technical articles, most of them focus on backend, middleware and stability testing, and compatibility testing has also been done specifically. In this article, I would like to share some of my views based on my understanding of compatibility testing and some experience in technical projects.
How to understand compatibility testing
Compatibility testing is initially to check whether the software can run normally on different hardware, operating systems and software platforms, that is, the portability and correctness of the software. Operating systems such as Windows and Mac, compatible with various browsers such as Chrome, Firefox, IE.
In recent years, with the overall development of the mobile Internet, when we mention compatibility testing, it refers more to the compatibility of software/APPs on different mobile devices and different operating systems, such as fonts, colors, resolutions, screen sizes, page sizes, etc. layout etc.
Mobile devices, that is, our common brands of mobile phones and tablets; operating systems, and now the mainstream are Android and IOS. Of course, in order to solve the problem of cross-platform compatibility of mobile terminals, H5 has become the de facto standard since it was proposed in 2004 and 14 years later. In recent years, with the vigorous development of the mini-program ecosystem, more and more attention has been paid to the compatibility of mini-programs.
Test Points for Compatibility Testing
As mentioned above, the points to be tested for compatibility mainly focus on five aspects: device type, operating system, network environment, page layout and resolution.
-
Device type: Devices are mainly divided into mobile phones and tablets. In the actual test, according to the market share of different series of major brands, models are purchased through the combination of brand + series.
-
Operating system: The current operating systems of mobile devices are mainly Android and IOS. In terms of operating system compatibility, the system version compatibility of IOS is relatively better, and the backward compatibility will be better. Generally, it can be tested with an emulator. Due to the customized development of major manufacturers, Android has its own characteristics. Therefore, when testing the compatibility of the operating system, it is necessary to consider the compatibility of various models, series, and versions. This is what the Android emulator does. Relatively poor. Of course, if you consider that the cost of buying a real phone is relatively high, you can consider the services provided by major cloud testing platforms, such as Baidu MTC, Ali MQC, Tencent Youtest and other platforms.
-
Network environment: The main test point of the network environment is the operation of the software APP in the case of mobile networks such as 3G, 4G, 5G, Wi-Fi, and weak networks.
-
Page layout: The main verification points of the page layout are buttons, styles, text display, Tab page switching and pictures. Especially for businesses such as games and cross-border e-commerce, which involve multiple languages, this aspect is the easiest to step on.
-
Screen resolution: The resolution of mainstream mobile devices is not too bad. During the test, we mainly focus on the screen resolution, screen size and UI adaptation of various device models. iOS can be tested through an emulator, and Android often still needs to be tested on a real device. If there is no high adaptation requirement for the screen size of the mobile phone, the emulator can be used for testing.
Notes on Compatibility Testing
-
If there is a high requirement for compatibility, a lot of manpower and hardware costs need to be invested for optimization, and continuous investment is required.
-
H5 and Native have their own advantages and disadvantages. The advantage of H5 lies in the convenience and scalability of cross-platform development, and the advantage of Native is that it has better native and device adaptability and is more stable.
-
After balancing the cost and effect, the relatively cost-effective compatibility test solution is to select mainstream models + operating systems for test verification, and use simulators/cloud test platforms to run automation to solve the rest.
-
In order to solve the compatibility problem of software APP, good R&D design specifications are necessary. For example, unified font/color for self-adaptation, default map crash map prompts, etc. for unified and standardized design.
Finally: The complete software testing video tutorial below has been organized and uploaded, and friends who need it can get it by themselves [Guaranteed 100% free]
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
