In our daily work, we often encounter the problem of web page incompatibility. The reason why we do compatibility testing is to ensure that the project to be tested runs normally on different operating system platforms.
It mainly includes that the project to be tested can run normally on different versions of the same operating system platform; the project to be tested can "peacefully coexist" with other related software or systems; the project to be tested can run normally in the specified hardware environment; the project to be tested The project can run normally in different network environments.
Although compatibility testing cannot guarantee complete quality, compatibility testing is an essential step for a project. Today, let's discuss the testing methods and some precautions for these compatibility issues one by one.
Main types of Web compatibility tests: Web compatibility tests are mainly tests for different operating system platforms, browsers, and resolutions.
01. Operating system compatibility
There are many different operating system types in the market, the most common ones are Windows, Unix, Macintosh, Linux, etc. Which operating system the end user of the Web application system uses depends on the configuration of the user system.
In this way, compatibility problems may occur, and the same application may run normally under some operating systems, but may fail to run under another operating system.
Therefore, before the release of the Web system, it is necessary to test the compatibility of the Web system under various operating systems.
Common operating systems include Windows, Unix, Linux, etc. For ordinary users, the most commonly used operating system is Windows. Windows operating system includes Windows XP, windows 2003, vista, Win2000/NT, Windows9x and so on.
The type of operating system used by the user directly determines the number of operating system platforms for our operating system platform compatibility test. The main purpose of the operating system platform compatibility test is to ensure that our project to be tested can run normally under the operating system platform .
For some special projects (such as customized projects), a certain type of operating system version can be specified, which should be specified in the requirements specification, and compatibility testing must be carried out for these specified operating system versions.
Most other projects do not specify the operating system version. For such projects, we should conduct compatibility tests for the current mainstream operating system versions. The system version is tested, and the integrity of the compatibility test of the operating system version of the project is ensured as much as possible.
02. Browser Compatibility
The browser is the core component of the Web client, and browsers from different manufacturers have different supports for Java, javascript, ActiveX, plug-ins or different HTML specifications.
For example, ActiveX is a product of Microsoft and was designed for Internet Explorer, javascript is a product of Netscape, Java is a product of Sun, and so on. Also, frame and hierarchy styles are displayed differently in different browsers, or not displayed at all. Different browsers have different settings for security and Java.
One way to test browser compatibility is to create a compatibility matrix. In this matrix, the adaptability of certain components and settings to different vendors and different versions of browsers is tested.
The browser is the core component of the Web system. Browsers from different manufacturers have different support for Javascrīpt, ActiveX or different HTML specifications. Even browsers from the same manufacturer have different versions. Different browsers have different settings for security and JAVA.
The most commonly used browsers are:
(1) Common browsers with IE kernel include: IE6, IE7, IE8, IE9, IE10, IE11, 360 Safe Browser (compatibility mode), 360 Speed Browser (compatibility mode), Sogou Browser (compatibility mode), QQ browser, etc.;
(2) The common browser of the Firefox kernel is the Firefox browser (Firefox);
(3) Common browsers with Chrome kernel include: Chrome, 360 Secure Browser (Extreme Speed Mode), 360 Extreme Speed Browser (Extreme Speed Mode), Sogou Browser (High Speed Mode).
For some special projects (such as customized projects), a certain type of browser (including version) can be specified, which must be specified in the requirements specification. Compatibility testing must be performed for these mainstream browsers.
However, most of the projects cannot specify browsers. For such projects, we must target the current mainstream browsers (including versions) and ensure that the compatibility tests of mainstream browsers pass, and then non-mainstream Browsers (including versions) are tested to ensure the integrity of the browser compatibility test of the project as much as possible.
03. Resolution compatibility
The resolution test is to test that the page layout can be displayed normally in different resolution modes, and the fonts meet the requirements.
What resolution mode the user uses is unknown to us. Typically, certain resolutions are suggested in our requirements specification. For testing, specific tests must be performed for the resolutions suggested in the requirements specification.
Now common resolutions are 1024×768, 800×600. For the resolution specified in the requirements specification, the test must ensure that the test passes, but for other resolutions, in principle, it should be guaranteed as much as possible, but since this is not restricted in the requirements specification, to a certain extent, development often Refuse to make adjustments.
For projects that do not specify a resolution in the requirement specification, the test should be done on the premise of completing the compatibility test of the mainstream resolution, and try to conduct some compatibility tests of non-mainstream resolutions to ensure most of them to a certain extent.
04. Internet speed test
The project to be tested can run the test normally in different network environments, and the speed limit test can be set through software such as Fiddler and 360 plug-ins.
05. Printer
Users may print the web page. Therefore, printing issues should be considered when designing web pages, and attention should be paid to saving paper and ink. Many users prefer to read rather than stare at the screen, so it is necessary to verify whether the web page printing is normal. Sometimes the alignment of pictures and text on the screen may not be the same as when printed. At a minimum, the tester needs to verify that the order confirmation page prints properly.
06. Combination test
Finally, a combined test is required. A resolution of 600x800 might look fine on a MAC, but it's ugly on an IBM compatible.
It can be displayed normally using Netscape on the IBM machine, but cannot be browsed using Lynx. If it's a web site for internal use, testing might be easier. If your company specifies a certain type of browser, test only on that browser.
If everyone uses T1 leased lines, there may be no need to test the download application. (But it should be noted that there may be employees dialing into the system from home) For some internal applications, the development department may state in the system requirements that some systems are not supported but only those that have been set up.
Ideally, however, the system would run on all machines so that future development and changes would not be restricted.
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:
Software testing interview applet
The software test question bank maxed out by millions of people! ! ! Who is who knows! ! ! The most comprehensive quiz mini program on the whole network, you can use your mobile phone to do the quizzes, on the subway or on the bus, roll it up!
The following interview question sections are covered:
1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux
6. web, app, interface automation, 7. performance testing, 8. programming basics, 9. hr interview questions, 10. open test questions, 11. security testing, 12. computer basics
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. I hope it can help you too!