One: The concept of compatibility testing : it is a test process to verify whether the developed program can operate normally and whether there is any abnormality in combination with specific software, hardware or data in a specific operating environment.
Two: Classification of compatibility tests:
(1) Browser Compatibility Test
It refers to checking the display effect of the web page style and elements on the browser , and whether the interaction is normal.
Major browsers:
Windows : IE, Firefox, Google .
Mac: safari, firefox, google.
Precautions:
1. Browser compatibility testing is common in products with a B/S (browser/server) structure.
2. Although we can collect mainstream browsers and corresponding versions through some official statistics, it is best for the product manager to clearly define which browsers and corresponding versions are supported, because it also depends on the application population and the corresponding version of the product. Specific business scenarios.
3. The browser compatibility test mainly checks the display effect of the web page style and elements, and whether there is any abnormality in the interaction, and has nothing to do with the specific business logic.
4. Communicate more with the front-end developers to clarify which styles or elements are not standard, and there may be compatibility issues. Now, we need to conduct targeted verification on all browser versions that require support, and select each browser A version of that validates all standard pages.
5. Make more records , summarize more, and do a good job of statistical analysis. In subsequent tests, you only need to test elements and styles that have changed and are prone to compatibility problems.
6. Pay attention to major version upgrades of IE, as well as iterative version updates of Google and Firefox, read the updated version notes to find out whether there are major changes that may affect the display and interaction of the page, and perform compatibility tests in a planned way.
(2) Operating system compatibility test
Checks for proper product functionality on the specified operating system.
Windows system, Macosx series, linux system, ios system.
Notes on testing:
1. It is common in products with a C/S (client/server) structure, and applications in the Internet era are also C/S structures in a broad sense.
2. The basic precautions are the same as the above browser compatibility test. It should be noted that the default permission levels of different versions of the operating system will be different, which will cause errors when the client needs to access or call system components or methods. .
3. When a major version of the same type of operating system is upgraded, it is necessary to pay attention to whether the library functions of the old version are still compatible in the new version or patch.
(3) Multi-version compatibility test
It is a test to verify whether the new version of the server side supports the new/old version of the client at the same time.
Notes on testing:
1. This is where many product managers tend to overlook design requirements, and it is also the biggest difference between C/S products and B/S products from the perspective of compatibility.
2. After the product is upgraded, the server will only have the latest version, but the client may have an old version due to different user scenarios. One reason is that there is no mandatory update and users do not choose to upgrade; the other reason is that in some enterprises In a low-level environment, the profiler package is upgradable depending on the policy of the administrator.
3. For client products, the test is relatively simple. As long as the server is upgraded every time, the old interface will not be modified due to new requirements, basically there will not be too many compatibility problems.
4. The test is relatively complicated for those client products that have both merchant version and user version. For functions that frequently interact, it is necessary to focus on compatibility testing of new and old versions.
(4) Data compatibility test
Because of the need for new functions, the upgrading and transformation of existing functions involves the verification of reading and writing of existing data, so as to ensure the normal flow of data between the new and old versions.
Notes on testing:
1. Forward compatibility, the new version of the software must be able to read and load the data generated by the old version normally and correctly.
2. Backward compatibility, the current version of the software must be able to support normal operation on subsequent higher version platforms.
3. For common office software or multimedia production or playback software, it is not only necessary to consider whether the new version of the client can correctly read the files generated by the old version, but also whether the files generated by the new version can be used normally by the old version of the client. The fire certificate has a corresponding upgrade prompt message.
4. There is another type of common order data, which is more related to the migration and conversion of background historical data. This part of the content also needs to be focused on to ensure that the migrated and converted data can be read correctly by users.
(5) Resolution Compatibility Test
Also known as adaptability testing, it refers to the testing process of verifying that the tested webpage or product UI can be displayed normally on monitors with various resolutions and mobile devices with various resolutions and screen sizes.
Notes on testing:
1. The one that needs to be paid attention to is the ordinary resolution screen, and the other is the high-definition resolution screen.
2. The issues that need attention mainly include whether the display is complete, whether the picture is stretched, and whether the position of the text and the picture is misaligned.
(6) Precautions
Mainstream browser (B/S): IE Firefox Chrome.
1. Compatibility depends on the product's application population and specific business scenarios.
2. Mainly check the display effect of the WEB page style and elements, and whether there is any abnormality in the interaction.
3. Communicate with the front end, clarify which styles and elements are not standard, and verify them in a targeted manner.
4. Pay attention to the update of the major version of the browser.
Mainstream operating systems (C/S): WINDOWS, MacOSX series, UNIX/LINUX series, Android series, iOS series.
1. Pay attention to the different permissions of the operating system, which leads to errors in the system components or methods accessed and called by the client.
2. Major version upgrade of the operating system, pay attention to whether the new version is compatible with the library functions of the old version.
3. Product upgrade - the server is the latest version - the client is displayed differently because it can be selectively updated or not.
4. Single-client products - to ensure that each upgrade of the server will not modify the old interface due to new requirements, and there is no problem with basic compatibility.
5. Merchant version (user version) - client. For functions that interact frequently, focus on compatibility issues between new and old versions.
6. Data compatibility test: It involves reading and writing of existing data to ensure that both old and new versions can be transferred.
Precautions:
1. Forward compatibility;
2. Backward compatibility;
3. Whether office software and media software can be read normally, whether the new version can be read by the old version normally, and corresponding upgrade prompts;
4. Common order data reading problems, whether the business process is running normally;
5. Data compatibility, migration and conversion of related back-end historical data;
6. Compatible resolution: it is UI.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Partners can click the small card below to receive