Web testing highlights

1. LINK TEST
(1) test whether all links are actually linked to the link page as instructed;
(2) test whether the linked page exists;
(3) ensure that there are no isolated pages on the web application system (isolated pages refer to websites that do not have links to the pages and can be accessed only by knowing the correct URL address ).
2. form Test
(1) Registration, login, and information submission must test the integrity of the submitted operations to verify the correctness of the information submitted to the server;
(2) Whether the date of birth and occupation entered by the user are appropriate, and whether the province and city of the user are matched;
(3) verify the correctness of default values;
(4) If the form can only accept specified values, skip these characters during testing to see if the system reports an error.
3. Cookies test (Session test is the same)
(1) Whether cookies work;
(2) Whether cookies are saved at a scheduled time;
(3) What is the impact of refreshing on cookies.
4. Design Language Testing
(1) which version of HTML is used;
(2) verify different scripting languages. For example, Java, javascr Using Pt, ActiveX, vbscr Using Pt or Perl.
5. Database Testing
(1) Data Consistency error: mainly because the form information submitted by the user is incorrect;
(2) Output Error: mainly caused by network speed or program design problems.
Ii. Performance Testing
1. connection speed test
(1) web system response time;
(2) Timeout restrictions.
2. Load Testing
(1) Number of users simultaneously accessing the web system at a certain time point;
(2) The quantity of online data processing.
3. Stress Testing
(1) stress testing tests System Restrictions and fault recovery capabilities, that is, to test whether the web application system will crash and under what circumstances. Hackers often provide wrong data load until the web application system crashes and then obtain access right when the system restarts.
(2) The stress testing area includes forms, login pages, and other information transmission pages.
Iii. Availability Test
1. Navigation Test
(1) intuitive navigation
(2) Whether the main part of the web system can be accessed through the home page
(3) does the system need site maps, search engines, or other navigation help?
(4) Whether the Page Structure, navigation, menu, and connection style of the Web application system are consistent
(5) Web Application System navigation help should be as accurate as possible. Once the level of the Web application system is determined, you must test the user navigation function.
2. Graphic Testing
A Web application system can contain images, animations, borders, colors, fonts, backgrounds, and buttons. The graphic test content includes:
(1) Ensure that the image has a clear purpose. Do not pile up images or Animations together to avoid wasting transmission time;
(2) The image size of the Web application system should be as small as possible, and a clear description of a specific thing should be provided, generally linked to a specific page;
(3) Verify that the font styles of all pages are consistent;
(4) the background color should be matched with the font color and foreground color;
(5) the size and quality of images are also an important factor. jpg or GIF compression is generally used.
3. content testing
Verify the correctness, accuracy, and relevance of information provided by the web application system.
Whether the information is correct indicates whether the information is reliable or mistakenly transmitted.
4. Overall Interface Test
The overall interface refers to the Page Structure Design of the entire web application system, which gives users a holistic sense. For example, do users feel comfortable when Browsing Web application systems? Do they intuitively know where the information they are looking for is? Is the design style of the entire web application system consistent? Of course, the overall test of the interface cannot be evaluated by personal intuition. The aesthetics, professional perspective, industry and users oriented to the system, and even gender and age of each person, these are all factors that may lead to different comments on the interface. Therefore, we need to understand that the entire interface testing process is actually a process of investigating the end user. Generally, the Web application system conducts a questionnaire on the homepage to obtain feedback from the end user.
Iv. Compatibility testing
1. Platform Testing
Before the web system is released, you need to test the compatibility of the web system under various operating systems.
2. browser testing
(1) the browser is the core component of the Web Client,, javascr ī PT, ActiveX, plug-ins, or different HTML specifications have different support. For example, ActiveX is a Microsoft product, designed for Internet Explorer, javascr platinum PT is a Netscape Product, and Java is a sun product. In addition, the frameworks and hierarchies are displayed differently in different browsers, or even not at all. Different browsers have different security and Java settings.
(2) One way to test browser compatibility is to create a compatibility matrix. In this matrix, the adaptability of browsers of different vendors and versions to some components and settings is tested.
V. Security Testing
(1) The current web application system is basically registered first, and then logged on. Therefore, you must test valid and invalid user names and passwords. You must check whether the user name is case sensitive, how many times can be tried, and whether the user can directly browse a page without logging in;
(2) Whether the web application system has a timeout limit. After logging on to the system, the user does not click any page within a certain period of time (for example, 15 minutes). Do you need to log on again to make the system work normally;
(3) to ensure the security of the Web application system, it is necessary to test whether the relevant information is written into the log file and traceable;
(4) When secure sockets are used, it is also necessary to test whether the encryption is correct and check the information integrity;
(5) server scripts often constitute security vulnerabilities, which are often exploited by hackers. Therefore, you must test whether the script cannot be placed or edited on the server without authorization.
(6) copy the URL of a functional point of a Web application in the form of simulated attacks, enter the URL address on the new page to check whether the URL can be accessed directly from the logon module of the system.
(7) check whether the default document function is set for IIS on the server.
(8) The main directory of the IIS server should be set in a different drive letter from the installation path of the operating system.

Http://www.rjgc.net/control/content/content.php? Nid = 15212