Testing method
1 Page link Check whether each link has a corresponding page, and the switching between pages is correct;
2 Relevance Check Whether deleting/adding one item will affect other items, and if so, whether these effects are correct.
3 Check whether the functions of the buttons are correct, such as update, cancel, delete, save and other functions are correct.
4 Check the length of the string Enter the content that exceeds the length of the string specified by the requirements, and see if the system checks the length of the string and whether there will be an error.
5Character type check Enter other types of content where the specified type of content should be input (such as input other character types where integers should be input), and see if the system checks the character type and reports an error.
6 Punctuation mark check The input content includes various punctuation marks, especially spaces, various quotation marks, and the carriage return key. See if the system handles it correctly.
7 Chinese character processing Input Chinese in a system that can input Chinese, and see if there will be garbled characters or errors.
8 Check the integrity of the information brought out. When checking the information and update information, check whether all the filled information is brought out. Whether the information brought out is consistent with the added information
9 Duplication of information In some information that needs to be named and the name should be unique, enter the duplicate name or ID to see if the system handles it and whether it will report an error. The duplicate name includes whether it is case-sensitive, and if you enter spaces before and after the input content, whether the system Do it right.
10 Check the delete function In some places where multiple messages can be deleted at one time, do not select any message, press "delete" to see how the system handles it, and see if there is an error; then select one or more messages and delete to see if they are processed correctly.
11 Check whether the addition and modification are consistent. Check whether the requirements for adding and modifying information are consistent. For example, if you add an item that is required to be filled, the modification should also be required; if you add an item that is specified as an integer, the modification must also be an integer.
12 Check and modify the duplicate name. When modifying, change the item that cannot be duplicated to the existing content, see if it will be processed, and an error will be reported. At the same time, pay attention to whether it will report an error with the same name as yourself.
13Repeatedly submit a record that has been successfully submitted in the form, and submit it after back to see if the system has processed it.
14 Check the situation of using the back key multiple times. In the place where there is back, back, return to the original page, and then back, repeat several times to see if there will be errors.
15Search check Input the content that exists or does not exist in the system where there is a search function to see if the search result is correct. If you can enter multiple search conditions, you can add reasonable and unreasonable conditions at the same time to see if the system handles it correctly.
16 Input information position Pay attention to whether the cursor and the input information will jump to other places when inputting information at the place where the cursor stays.
17 Upload and download files Check whether the function of uploading and downloading files is realized, and whether the uploaded files can be opened. What are the regulations on the format of uploaded files, whether the system has explanation information, and check whether the system can do it.
18 Mandatory key Check whether the system has processed all the items that should be filled in if they are not filled in, and whether there is a prompt message for the required items, such as adding * before the required items
19 Shortcut keys Check whether it supports common shortcut keys, such as Ctrl+C Ctrl+V Backspace, etc. For some fields that do not allow input information, such as selecting people and selecting dates, whether the shortcuts are also restricted.
20 Enter key check Press the Enter key directly after the input to see how the system handles it and whether an error will be reported.
function test
1.1. Link test
Link is a main feature of Web application system, it is the main means to switch between pages and guide users to some pages whose addresses are unknown. Link testing can be divided into three aspects. First, test whether all links are indeed linked to the linked page as indicated; second, test whether the linked page exists; finally, ensure that there are no orphaned pages on the web application system. The so-called orphaned page means that there is no link pointing to the page , you can only access it if you know the correct URL address.
Link testing can be automated and there are many tools available today. Link testing must be completed in the integration testing phase, that is, link testing is performed after all pages of the entire Web application system have been developed.
1.2. Form testing
When users submit information to the web application system administrator, they need to use form operations, such as user registration, login, information submission, and so on. In this case, we must test the integrity of the commit operation to verify the correctness of the information submitted to the server. For example: whether the date of birth and occupation filled in by the user are appropriate, whether the filled province and city match, etc. If the default value is used, also verify the correctness of the default value. Also test if the form can only accept certain values specified. For example: only certain characters can be accepted, and these characters can be skipped during the test to see if the system will report an error.
1.3. Cookies test
Cookies are usually used to store user information and user operations in an application system. When a user visits an application system using Cookies, the Web server will send information about the user and store the information in the form of Cookies on the client computer. On , this can be used to create dynamic and custom pages or to store information such as logins.
If the Web application system uses Cookies, it is necessary to check whether the Cookies can work normally. The content of the test may include whether Cookies work, whether they are saved according to the scheduled time, and what impact refresh has on Cookies, etc.
1.4. Design Language Test
Differences in web design language versions can cause serious problems on the client or server side, such as which version of HTML to use, etc. This problem is even more important when developing in a distributed environment where developers are not together. In addition to HTML version issues, different scripting languages such as Java, JavaScript, ActiveX, VBScript or Perl also need to be verified.
1.5. Database testing
In the Web application technology, the database plays an important role, and the database provides space for the management, operation, query and realization of the user's request for data storage of the Web application system. In Web applications, the most commonly used database type is a relational database, which can use SQL to process information.
In a Web application system using a database, generally, two types of errors may occur, namely, data consistency errors and output errors. Data consistency errors are mainly caused by incorrect form information submitted by users, while output errors are mainly caused by network speed or program design problems. For these two situations, tests can be performed separately.
Performance Testing
2.1. Connection speed test
The speed at which users connect to the Web application system varies according to the way they access the Internet. They may be dialing up the phone or surfing the Internet through broadband. Users can wait a long time when downloading a program, but not if only visiting a page. If the web system takes too long to respond (for example, more than 5 seconds), users will leave impatiently.
In addition, some pages have a timeout limit. If the response speed is too slow, users may need to log in again before they have time to browse the content. Moreover, if the connection speed is too slow, it may also cause data loss, so that the user cannot get the real page.
2.2. Load test
Load testing is to measure the performance of the web system at a certain load level, so as to ensure that the web system can work normally within the required range. The load level can be the number of users accessing the web system at the same time at a certain moment, or the number of online data processing. For example: How many users can the web application system allow to be online at the same time? What happens if this amount is exceeded? Can the web application system handle a large number of user requests for the same page?
2.3. Stress test
The load test should be arranged in the actual network environment after the release of the Web system. Because the internal staff of an enterprise, especially the project team, is always limited, and the number of requests that a web system can handle at the same time will far exceed this limit, so the result is only correct if it is placed on the Internet and subjected to load testing Believable.
Stress testing refers to actually destroying a Web application system and testing the reflection of the system. Stress testing is to test the limitations and fault recovery capabilities of the system, that is, to test whether the web application system will crash and under what circumstances it will crash. *** often serve the wrong data payload until the web application system crashes, and then gain access when the system restarts.
Areas to stress test include forms, logins, and other information transfer pages.
usability testing
3.1. Navigation test
Navigation describes the way users operate within a page, between different user interface controls, such as buttons, dialog boxes, lists, and windows, etc.; or between different connected pages. You can determine whether a Web application is easy to navigate by considering the following questions: Is the navigation intuitive? Are major parts of the web system accessible through the home page? Does the Web system need a site map, search engine, or other navigation aid?
Putting too much information on one page can often have the opposite effect than intended. Users of web application systems tend to be purpose-driven, and quickly scan a web application system to see if there is information that meets their needs, and if not, they will leave quickly. Few users are willing to take the time to familiarize themselves with the structure of the Web application system, so the navigation help of the Web application system should be as accurate as possible.
Another important aspect of navigation is whether the page structure, navigation, menu, and connection styles of the Web application system are consistent. Make sure that users intuitively know whether there is content in the Web application system and where the content is.
Once the level of the Web application system is determined, it is necessary to test the user navigation function, and let the end users participate in this test, and the effect will be more obvious.
3.2. Graphics test
In the Web application system, appropriate pictures and animations can not only play the role of advertising, but also beautify the page. The graphics of a web application system can include pictures, animations, borders, colors, fonts, backgrounds, buttons, etc. Graphics tests include:
(1) To ensure that the graphics have a clear purpose, pictures or animations should not be piled up randomly, so as not to waste transmission time. The image size of the web application system should be as small as possible, and it should be able to clearly explain something, generally linking to a specific page.
(2) Verify that all page font styles are consistent.
(3) The background color should match the font color and foreground color.
(4) The size and quality of the picture is also a very important factor, generally using JPG or GIF compression.
3.3. Content Testing
Content testing is used to verify the correctness, accuracy and relevance of the information provided by the Web application system.
The accuracy of information refers to whether the information is reliable or misinformed. For example, in a commodity price list, wrong prices may cause financial problems and even legal disputes; the accuracy of information refers to whether there are grammatical or spelling mistakes. This kind of test is usually carried out using some word processing software, such as using the "Pinyin and Grammar Check" function of Microsoft Word; the relevance of information refers to whether the information list or entry related to the current browsing information can be found on the current page, that is, A so-called "related article list" in a typical Web site.
3.4. Overall interface test
The overall interface refers to the page structure design of the entire Web application system, giving users a sense of integrity. For example: Do users feel comfortable when browsing the Web application system, and do they intuitively know where the information they are looking for is? Is the design style of the entire web application system consistent?
The process of testing the overall interface is actually a process of investigating end users. Generally, Web application systems take the form of a questionnaire on the home page to obtain feedback information from end users.
As with all usability testing, the involvement of outsiders (people with little or no connection to Web application development), preferably end users, is required.
Client Compatibility Testing
4.1. Platform testing
There are many different operating system types on 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 conduct a compatibility test on the Web system under various operating systems.
4.2. Browser testing
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.
security test
The security testing areas of the web application system mainly include:
(1) The current web application system basically adopts the method of registering first and then logging in. Therefore, you must test valid and invalid usernames and passwords, pay attention to whether they are case-sensitive, limit how many times you can try, whether you can directly browse a certain page without logging in, etc.
(2) Whether the web application system has a timeout limit, that is, if the user does not click on any page within a certain period of time (for example, 15 minutes) after logging in, whether it needs to log in again to use it normally.
(3) In order to ensure the security of the Web application system, log files are very important. It is necessary to test whether the relevant information is written into the log file and whether it can be traced.
(4) When a secure socket is used, it is also necessary to test whether the encryption is correct and check the integrity of the information.
(5) Server-side scripts often constitute security holes, and these holes are often exploited by hackers. Therefore, it is also necessary to test the problem that scripts cannot be placed and edited on the server side without authorization.
Summarize
This article discusses the web-based system testing method in terms of functionality, performance, usability, client compatibility, security, etc.
Web-based system testing has similarities and differences with traditional software testing, which brings new challenges to software testing. Web-based system testing not only needs to check and verify whether it operates according to the design requirements, but also evaluates whether the system displays properly on different users' browsers. It is important to also conduct security and usability testing from an end-user perspective.
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