Web test points to do the mobile end of the test, also do web-side testing, and even the back of the desktop test and background testing has done, basically put our products all the end of play a round

Web Test Essentials

first, the function Test

1, Link testing
(1), test that all links are actually linked to the linked page as instructed; 
(2), test whether the linked page exists; 
(3), guaranteeWebThere are no orphaned pages on the application system(The so-called orphaned page refers to the page without a link, only knowing the correctURLAddress to access).  

2, form testing
(1), registration, login, information submission, etc., must test the integrity of the submission operation to verify the correctness of the information submitted to the server;
(2), the user to fill in the date of birth and occupation is appropriate, fill in the province and the city is matching; 
(3), verify the correctness of the default values;
(4, such as the form can only accept certain values specified, skip these characters when testing to see if the system will error.

3, cookies test (session test with )
( 1 cookies    
( 2", cookies Whether to save at a predetermined time;
( 3 cookies what is the impact.    

4
( 1 html
( 2 java javascrīpt activex or perl

5. Database Testing
(1), data consistency error: Mainly due to the user submitted form information is incorrect;
(2), output error: Mainly due to network speed or programming problems caused by.  

Second, performance testing

1, connection speed test
( 1), web System response time,
( 2

2 load test
( 1 web The number of users of the system;
( 2

3. Pressure test
(1), stress testing is the test system limitations and failure recovery capabilities, that is, testing the Web application system will not crash, under what circumstances will crash. Hackers often provide incorrect data loads until the Web application crashes and then gain access when the system restarts.
(2), the pressure test area includes forms, landing and other information transmission pages.

Iii. Usability Testing

1, navigation testing
(1), navigation is intuitive
(2),Webwhether the main part of the system can be accessed via the homepage 
(3), if the system requires a sitemap, search engine, or other navigational aids 
(4),WebApplication System's page structure, navigation, menu, connection style is consistent 
(5),Webapply system navigation help to be as accurate as possible. Webonce the hierarchy of the application system is decided, it is necessary to test the user navigation function.

2, Graphics testing
aWebthe graphics of the application system 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;
(2),WebApplication system picture size to be as small as possible, and to be able to clearly explain something, generally linked to a specific page;
(3), verify that the style of all page fonts is consistent;
(4), the background color should match the font color and the foreground color;
(5), the size and quality of the picture is also a very important factor, generally usingJPGorGIFcompression.

3, Content testing
InspectionWebThe application system provides the correctness, accuracy and relevance of the information.
The correctness of information refers to whether the information is reliable or misinformation .

4, overall interface testing
The overall interface refers to the entireWebapplication of the system page structure design, is to give users a sense of the whole. For example, when a user browsesWebDo you feel comfortable applying the system, and do you intuitively know where to find the information? WholeWebare the design styles of the application system consistent? Of course, the overall test of the interface can not be assessed by personal intuition alone, everyone's aesthetic, professional perspective, system-oriented industry and users, and even gender and age, etc., are likely to lead to different evaluation of the interface factors. So understand that in the testing process of the overall interface, it is actually a process of investigating the end user. GeneralWebThe application system takes the form of a questionnaire on the homepage to get feedback from the end user.

Iv.. Compatibility test

1. Platform Testing
in the Before a Web system is published, the web system needs to be tested for compatibility under various operating systems .

2, Browser testing
(1), the browser isWebThe core components of the client, from different vendors of the browser toJava, andjavascrīpt,ActiveX,Plug-insor a differentHTMLspecifications have different support. For example,ActiveXis aMicrosoftthe product is forInternet Explorerand the design,javascrīptis 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.
(2), 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.

v. Safety testing
(1), the currentWebthe application system basically uses the first registration, after landing the way. Therefore, you must test valid and invalid user name and password, to notice whether the case is sensitive, you can try how many times the limit, whether you can not login and directly browse a page, and so on;
(2),Webdoes the application have a timeout limit, after the user logs in for a certain amount of time (e.g. theminutes) Do not click on any page, whether the need to re-login to normal use;
(3), in order to ensureWebApplication system security, need to test whether the relevant information is written into the log file, can be traced;
(4), when using a secure socket, also test encryption is correct, check the integrity of the information; 
(5), server-side scripting often poses a security vulnerability that is 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.
(6), copied in the form of a simulated attackWebof a function point of the application.URLaddress, and then open a new page to enter theURLaddress to see if it can cross the system's login module directly into the function point.
(7), server-sideIISwhether the default document feature is set.
(8),IISThe server's home directory should be set under a different drive letter than the operating system's installation path.  

Web test points to do the mobile end of the test, also do web-side testing, and even the back of the desktop test and background testing has done, basically put our products all the end of play a round