Summary of Web test methods

Summary of WEB test methods

Web -based system testing in the development of Web -based systems, in the absence of rigorous processes, we develop, publish, implement, and maintain the Web , There may be some serious problems and the likelihood of failure is great. And, as Web -based systems become more complex, a failure of one project can lead to many problems.

In web engineering process, based on web web system testing differs from traditional software testing, It not only needs to check and verify whether to run according to the requirements of the design, but also to test the system in different user's browser display is appropriate. It is important to also test security and usability from the perspective of the end user. However, internet and web web Span style= "font-family: the song Body;" The system becomes difficult. Therefore, we have to test and evaluate the complex based on the web web The app's release cycle is calculated in days or even in hours.

　　Web Testers have to deal with shorter release cycles, and testers and test managers face a legacy from testing C/S Structural and framework environments to test fast-changing Web the transformation of the application system.

first, functional testing 1. Link Test

Link is a main feature of WEB application system, it is the main means to switch between pages and instruct users to go to some pages that do not know the address. Link testing can be divided into three areas. First, test that all links are indeed linked to the linked page as instructed, and secondly, whether the linked pages exist, and finally, to ensure that there are no orphaned pages on the Web application System, so-called orphaned pages are no links to the page, only the correct URL address to access. Link testing can be done automatically, and now there are many tools to take. Link testing must be done during the integration testing phase , that is, link testing after all page development of the entire WEB application system is completed.

2. Form Testing

When users submit information to the WEB application administrator, they need to use form actions, 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: The user fills in the birth date and the occupation is appropriate, fills in the province and the city whether matches and so on. If a default value is used, verify that the default value is correct. If the form can only accept certain values that are specified, it is also tested. For example, only certain characters can be accepted, and these characters may be skipped during testing to see if the system will make an error.

3.Cookies Test

Cookies are typically used to store user information and the user's actions in an application, and when a user accesses an application using Cookies ,theWeb The server sends information about the user and stores the information in the form of Cookies on the client computer, which can be used to create dynamic and custom pages or to store login information. If the Web application uses cookies, it is necessary to check whether the cookies work properly. The content of the test may include whether the cookie is working, whether it is saved at the scheduled time, and what effect the refresh has on cookies .

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 . This issue is especially important when developers are not together when developing in a distributed environment. In addition to the HTML version problem, different scripting languages, such as Java,JavaScript, authentication is also done for ActiveX, VBScript, or Perl.

5. Database Testing

In the Web application technology, the database plays an important role, and the database provides the space for the management, operation, query and realization of the user's request to the data storage. in Web applications, the most common type of database is a relational database, and you can use SQL to process information. In a Web application system that uses a database, there are generally two types of errors that can occur, namely, data consistency errors and output errors. Data consistency errors are mainly caused by incorrect form information submitted by users, and output errors are mainly caused by network speed or programming problems, which can be tested separately for both cases.

Performance Testing 1. connection Speed Test

The speed at which users connect to Web applications varies depending on how they surf the internet, and they may be telephone dialing or broadband access. When downloading a program, the user can wait a long time, but if you only visit a page it will not. If the response time of the Web system is too long ( For example, more than 5 seconds ), the user will leave without patience. In addition, some pages have a timeout limit, if the response is too slow, the user may not have time to browse the content, you need to re-login. Moreover, the connection speed is too slow, may also cause the data loss, causes the user to get the real page.

2. Load Test

Load tests are designed to measure the performance of a Web system at a certain load level to ensure that the Web system functions properly within the requirements range. The load level can be the number of users who have access to the Web system at any one time , or the amount of online data processing. For example: How many users can a WEB application be allowed to be online at the same time ? What happens if you exceed this amount? ? Can Web applications handle a large number of users ' requests for the same page ?

3. Stress Testing

The load test should be scheduled to be tested in the actual network environment after the WEB system is published. Because an in-house employee, especially a project team, is always limited, and the number of requests that a Web system can process at the same time will go far beyond this limit, so only on the Internet , Accept the load test and the result is correct and trustworthy. Stress testing refers to the actual destruction of a Web application System, the test system reflects. Stress testing is the ability to test system limitations and resiliency, which means that testing Web applications will crash and under what circumstances. Hackers often provide incorrect data loads until the Web application crashes and then gain access when the system restarts. Areas of stress testing include forms, landing, and other information transfer pages.

Usability Testing 1. Navigation test

Navigation describes how users operate within a page, between different user interface controls, such as buttons, dialogs, lists, and Windows.;or between different connection pages. By considering the following questions, you can decide on aWebwhether the application system is easy to navigate: Whether navigation is intuitive? Webwhether the main part of the system can be accessed via the homepage? Webwhether the system requires a sitemap, search engine, or other navigational aids?putting too much information on a page tends to have the opposite effect as expected. Webthe user of the application tends to drive the target and quickly scans aWebapplication System to see if there is information to meet their needs, if not, will quickly leave. Few users are willing to take the time to familiarize themselves withWebthe structure of the application system, therefore,Webapply system navigation help to be as accurate as possible. Another important aspect of navigation isWebThe page structure, navigation, menu, and connection styles of the application system are consistent. Make sure the user is intuitively awareWebis there content in the application system and where is the content? Webonce the hierarchy of application system is decided, it is necessary to test the user navigation function, let the end user participate in this kind of test, the effect will be more obvious. Software Testing

2. Graphics Testing

In the Web Application System, the appropriate picture and animation can play the role of advertising, but also to beautify the function of the page. A Web application's graphics can include pictures, animations, borders, colors, fonts, backgrounds, buttons, and so on.

The contents of the graphic test are:

(1) To ensure that the graphics have a clear purpose, the picture or animation do not randomly stacked together, so as not to waste transmission time. Web the image size of the application system should be as small as possible, and to be able to clearly describe something, usually linked 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 image is also a very important factor, generally using JPG or GIF compression.

3. Content Testing

The

Content test is used to verify web Application systems provide the correctness, accuracy, and relevance of information. The correctness of information refers to whether the information is reliable or misinformation. For example, in the list of commodity prices, the wrong price may cause financial problems or even lead to legal disputes microsoft Word " Pinyin and grammar check " function web in the site " related articles list "

4. Overall interface test

Overall interface refers to the entire Web Application System page structure design, is to give users a sense of the whole. For example: When a user is comfortable browsing a Web application, is it intuitive to know where to find the information ? Whole Web whether the design style of the application system is consistent ? The test process for the overall interface is actually a process of investigating the end user. The general Web application system takes the form of a questionnaire on the homepage to get feedback from the end user. For all usability testing, there is a need for external personnel ( people who are not connected or have little contact with Web Application development ) Participation, preferably end-user participation.

Client Compatibility Testing 1. Platform Testing

There are many different operating system types on the market, the most common of which are Windows,Unix,Macintosh,Linux and so on. which operating system the end users of WEB applications use depends on the configuration of the user's system. In this way, compatibility issues may occur, and the same application may run correctly under some operating systems, but may fail under another operating system. Therefore, before the Web system is published, the web system needs to be tested for compatibility under various operating systems .

2. Browser Testing

Browser isWebThe core components of the client, from different vendors of the browser toJava, andJavaScript,ActiveX,Plug-insor a differentHTMLspecifications have different support. For example,ActiveXis aMicrosoftthe product is forInternet Explorerand the design,JavaScriptis aNetscapeof products,Javais aSunproducts, and so on. In addition, frame and hierarchy styles are displayed differently in different browsers, not even at all. Different browsers for security andJavasettings are not the same. One way to test browser compatibility is to create a compatibility matrix. In this matrix, we test the adaptability of different vendors and different versions of browsers to certain components and settings.

Security Testing && software Testing

the security testing area of WEB application system mainly includes:

(1) The current Web Application System basically uses the first registration, after landing. Therefore, you must test the valid and invalid user name and password, to notice whether the case is sensitive, how many times you can try the limit, whether you can browse a page without landing and so on.

(2) Whether the Web application system has a time-out limit, that is, after the user login in a certain period of time ( such as minutes ) did not click on any page, If you need to log in again for normal use.

(3) In order to ensure the security of Web application System, log files are very important. You need to test whether the relevant information is written into the log file and is traceable.

(4) When a secure socket is used, it is also necessary to test whether the encryption is correct and to check the integrity of the information.

(5) server-side scripts often constitute security vulnerabilities that are often exploited by hackers. Therefore, you also want to test the problem of not being authorized to place and edit scripts on the server side.

Summary

This paper discusses the Web -based system testing method from the aspects of function, performance, usability, client compatibility and security. Web -based system testing has similarities and differences with traditional software testing, and presents new challenges to software testing. Web -based system testing not only needs to check and verify whether to run according to the requirements of the design, but also to evaluate whether the system is suitable for display on the browser side of different users. It is important to have security and usability measurements from the end-user perspective.

the actual operation method of WEB functional testing

WEB Functional testing is to verify the functions of the product, according to the functional test cases, test-by-item, check whether the product meets the user requirements of the function. The common testing methods for WEB applications are as follows:

2. Page link check: Whether each link has a corresponding page, and the page between the correct switch.
4. Dependency checking: Deleting / Adding an item will have an impact on other items, and if so, whether the effects are correct.
6. Check that the button is functioning correctly: such as update, cancel, Delete, save and other functions are correct.
8. String length check: Enter content that exceeds the length of the string indicated by the requirement, and see if the system checks the length of the string for errors.
10. Character type checking: Enter other types of content where the content of the specified type should be entered ( such as entering a different character type where the integer type should be entered )to see if the system checks the character type and whether it will error.
12. Punctuation check: The input includes various punctuation marks, especially spaces, various quotes, and enter . See if the system is working correctly.
14. Chinese character processing: In the system can input Chinese language, see if there will be garbled or error.
16. Check the integrity of the information that is brought out: when viewing the information and update information, check that the information you have filled out is not all taken out, and that the information and additions are consistent .
18. Information duplication: In some need to name, and the name should be unique information input duplicate name or ID, to see if the system has been processed, will be error, the same name includes whether the case-sensitive, as well as the input before and after the input space, the system to make the correct processing.
20. Check Delete function: In some can delete more information at once, do not select any information, press "Delete" to see how the system is handled, will be wrong ; then select one and more information to delete and see if it is handled correctly.

Summary of Web test methods