Web-based system testing In Web-based system development, if there is no strict process, we may encounter some serious problems in the process of development, release, implementation and maintenance of the Web, and the possibility of failure is very high. Moreover, as Web-based systems become more and more complex, the failure of a project may cause many problems. When this happens, our confidence in the Web and the Internet may be irretrievably shaken, causing a Web crisis. Moreover, the Web crisis may be more serious and more widespread than the software crisis faced by software developers.
In the process of Web engineering, the testing, confirmation and acceptance of Web-based systems is an important and challenging task. Web-based system testing is different from traditional software testing. It not only needs to check and verify whether it runs according to the design requirements, but also test whether the system is properly displayed on the browser side of different users. It is important to conduct security and usability testing from the perspective of the end user. However, the unpredictability of the Internet and Web media makes it difficult to test Web-based systems. Therefore, we must research new methods and technologies for testing and evaluating complex Web-based systems. The release cycle of general software is calculated in months or years, while the release cycle of web applications is calculated in days or even hours.
Web testers must deal with shorter release cycles. Testers and test managers are faced with a shift from testing the traditional C/S structure and framework environment to testing fast-changing Web application systems.
1. Functional test
1. Link test
Links are a main feature of Web application systems. They are the main means of switching between pages and guiding users to pages that do not know the address. Link testing can be divided into three aspects. First, test whether all links actually link to the linked page as instructed; second, test whether the linked page exists; finally, ensure that there is no isolated page on the web application system. The so-called isolated page means that there is no link to the page. , You can only visit if you know the correct URL address. Link testing can be automated, and many tools are now available. The link test must be completed in the integration test phase, that is, the link test is performed after the development of all pages of the entire Web application system is completed.
2. Form test
When users submit information to the Web application system administrator, they need to use form operations, such as user registration, login, and information submission. In this case, we must test the integrity of the submission operation to verify the correctness of the information submitted to the server. For example: whether the date of birth and occupation entered by the user are appropriate, whether the province and the city in which they are entered match, etc. If the default value is used, check the correctness of the default value. If the form can only accept certain values specified, it must also be tested. 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.
3. Cookies test
Cookies are usually used to store user information and user operations in a certain application system. When a user uses Cookies to access a certain application system, the Web server will send information about the user and store the information on the client computer in the form of Cookies. This can be used to create dynamic and custom pages or store login information. If the Web application system uses cookies, you must check whether the cookies can work properly. The content of the test may include whether the cookies work, whether they are saved at a predetermined time, and what impact refresh has on cookies, etc.
4. Design language test
Differences in web design language versions can cause serious problems on the client or server, such as which version of HTML to use. When developing in a distributed environment, developers are not together, this problem becomes particularly important. In addition to the version of HTML, different scripting languages, such as Java, JavaScript, ActiveX, VBScript, or Perl, must also be verified.
5. Database testing
In the Web application technology, the database plays an important role. The database provides space for the management, operation, query and realization of user requests for data storage of the Web application system. In Web applications, the most commonly used database type is a relational database, and SQL can be used to process information. In a Web application system that uses a database, in general, two types of errors may occur, which are 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 programming problems. For these two situations, tests can be performed separately.
Two, performance test
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 dial-up or broadband Internet access. When downloading a program, the user can wait a long time, but this will not be the case if only visiting a page. If the response time of the Web system is too long (for example, more than 5 seconds), the user will leave because of impatient waiting. In addition, some pages have timeout restrictions. If the response speed is too slow, the user may not have time to browse the content and need to log in again. Moreover, the connection speed is too slow, it may also cause data loss, so that users can not get the real page.
2. Load test
Load testing is to measure the performance of the Web system at a certain load level 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 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? If this number is exceeded, what will happen? Can the web application system handle a large number of users' requests for the same page?
3. Stress test
Load testing should be arranged in the actual network environment after the Web system is released. Because the internal employees of an enterprise, especially the project team personnel, are always limited, and the number of requests that a Web system can handle at the same time will far exceed this limit, so only on the Internet and accept the load test, the result is correct Credible. Performing a stress test refers to actually destroying a Web application system and testing the reflection of the system. Stress testing is to test the limitations and failure recovery capabilities of the system, that is, to test whether the Web application system will crash, and under what circumstances it will crash. Hackers often provide the wrong data load until the web application system crashes and then gains access when the system restarts. The area of the stress test includes forms, login and other information transmission pages.
Three, usability testing
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; or between different connection pages. You can decide whether a web application system is easy to navigate by considering the following questions: Is the navigation intuitive? Can the main parts of the web system be accessed through the homepage? Does the web system need site maps, search engines, or other navigation aids? On one page Putting too much information often has the opposite effect to expectations. Users of Web application systems tend to be purpose-driven, and scan a Web application system quickly to see if there is information that meets their needs. 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. Therefore, the navigation assistance 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 the user intuitively knows whether there is content in the web application system, and where the content is. Once the level of the Web application system is decided, it is necessary to start testing the user navigation function, let the end users participate in this test, the effect will be more obvious.
2. Graphic test
In the Web application system, appropriate pictures and animations can not only play the role of advertising, but also play the role of beautifying the page. The graphics of a web application system can include pictures, animations, borders, colors, fonts, backgrounds, buttons, and so on.
The contents of the graphic test are:
-
(1) Make sure that the graphics have a clear purpose, and the pictures or animations should not be piled together randomly, so as not to waste transmission time. The picture 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 the styles of all page fonts 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. Content test
Content testing is used to verify the correctness, accuracy and relevance of the information provided by the Web application system. The correctness of information refers to whether the information is reliable or misrepresented. For example, in the list of commodity prices, wrong prices may cause financial problems or even legal disputes; the accuracy of information refers to whether there are grammatical or spelling errors. This kind of test is usually carried out using some word processing software, such as using the pinyin and grammar checking functions 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, the general Web A list of so-called related articles on the site.
4. The overall interface test
The overall interface refers to the page structure design of the entire Web application system, which gives users a sense of integrity. For example: Does the user feel comfortable when browsing the Web application system, do they intuitively know where the information they are looking for? Is the design style of the entire Web application system consistent? The testing process of the overall interface is actually a process for the end user The process of investigation. Generally, Web application systems take the form of a questionnaire on the homepage to obtain feedback from end users. For all usability testing, it is necessary to have the participation of external personnel (people who have no contact with the development of the Web application system or have little contact), preferably the participation of the end user.
Four, client compatibility test
1. Platform test
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 issues may occur, and the same application may run normally under some operating systems, but may fail to run under other operating systems. Therefore, before the Web system is released, it is necessary to conduct compatibility tests on the Web system under various operating systems.
2. Browser test
The browser is the core component of the Web client. Browsers from different vendors have different support for Java, JavaScript, ActiveX, plug-ins or different HTML specifications. For example, ActiveX is a product of Microsoft, designed for Internet Explorer, JavaScript is a product of Netscape, Java is a product of Sun, and so on. In addition, the frame and hierarchy styles are displayed differently in different browsers, or even 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, test the adaptability of browsers of different vendors and versions to certain components and settings.
Five, safety test
The security test 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, it is necessary to test valid and invalid user names and passwords, pay attention to whether it is case sensitive, limit how many times can be tried, whether it is possible to browse a certain page directly without logging in, etc.
-
(2) Does the web application system have a timeout restriction, that is, if the user does not click on any page within a certain period of time (for example, 15 minutes) after logging in, does it need to log in again to use it normally?
-
(3) In order to ensure the security of the Web application system, log files are essential. Need to test whether the relevant information is written into the log file and whether it can be traced.
-(4) When using a secure socket, test whether the encryption is correct and check the integrity of the information.
- (5) Server-side scripts often constitute security vulnerabilities, and these vulnerabilities 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.
Six, summary
This article discusses Web-based system testing methods from the aspects of function, performance, usability, client compatibility, and security. Web-based system testing has both similarities and differences with traditional software testing, which poses new challenges to software testing. Web-based system testing not only needs to check and verify whether it is running according to the design requirements, but also to evaluate whether the system is properly displayed on the browser side of different users. It is important to conduct security and usability testing from the perspective of the end user.
Data sharing
This content comes from my collection and sorting in recent years, and the whole is organized around [software testing]. The main content includes: python automation test exclusive video, Python automation details, a full set of interview questions and other knowledge content.
For software testing friends, it should be the most comprehensive and complete interview preparation warehouse. In order to better organize each module, I also refer to many high-quality blog posts and projects on the Internet, and strive not to miss every knowledge point. Friends relied on these contents to review, and got offers from big factories such as BATJ. This warehouse has also helped many software test learners, and I hope it can also help you.
Pay attention to the official account: Programmer Erhei, you can get a complete set of software testing resource collection warehouse