Web Testing Basics

Web-based system testing and traditional software testing have both similarities and differences, posing new challenges to software testing. Web-based system testing requires not only checking and verifying whether the system runs according to the design requirements, but also evaluating whether the system displays properly on different users' browsers. It is important to test security and availability from the end user's perspective.

This article discusses Web-based system testing methods in terms of functions, performance, availability, client compatibility, and security.

Website test process, requirements and test report

After a website is basically completed, you must pass the following three steps to test the website.

1. Producer test, including the art test page and programmer test function. The producer himself will perform the test immediately after completion.

A) pages, including the Home Page, second-level page, and third-level page, are misplaced under various common resolutions; Are there any typos on the image; Are there connections dead links; whether the pictures and content of each topic correspond.

B) The function meets the customer's requirements. The database connection is correct. The dynamically generated connections are correct. The format and content of the passed parameters are correct. The test content is correct.

2. In accordance with the delivery standards and customer requirements, the comprehensive testing should be conducted by dedicated personnel.

It also includes two aspects: page and program, and should be combined for testing to ensure that the page will not be deformed after filling enough content. In addition, check whether there are typos and common sense errors in the text content.

3. Release the test website after it is released to the master server, mainly to prevent errors caused by different environments.

Main aspects of testing:

I. Function Testing

For website testing, each independent function module needs to design and export test cases separately, mainly based on the requirement specification and detailed design specification. for the application module, the designer must provide test cases for the basic path test method.

1. Link Testing: links are a major feature of Web application systems. They are the main means of switching between pages and guiding users to access pages with unknown addresses. Link testing can be divided into three aspects:

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 in the Web application system. The so-called isolated page means that there is no link to the page, and only the correct URL address can be accessed.

The link test can be performed automatically. Many tools are available now. The link test must be completed in the integration test phase, that is, the link test must be conducted after all pages of the web application system are developed.

2. form test: when you submit information to the Web Application System Administrator, you need to use form operations, such as user registration, login, and information submission. In this case, we must test the integrity of the submitted 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, and whether the province and city of the user are matched. If the default value is used, check whether the default value is correct. If the form can only accept specified values, the test is also required. For example, you can only accept certain characters. during testing, you can skip these characters to see if the system reports an error. To test these programs, verify that the server can properly store the data and that the programs running in the background can correctly interpret and use the information.

The main functions of the B/S structure are as follows: submit data and process data. If there is a fixed operation flow, you can consider the recording function of the automated testing tool, write reusable script code that can be run during testing and regression testing to reduce the workload of testers.

We will test the functions of each function module in the Um subsystem one by one. The main testing methods are: Boundary Value test, equivalence test, and exception test. In the test, ensure that each type has more than two input values of typical values to ensure the comprehensiveness of the test input.

3. Cookies test: cookies are usually used to store user information and user operations in an application system. When a user uses cookies to access an application system, the Web server sends user information, stores the information in the form of cookies on the client computer, and 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 work properly and the information is encrypted. The test content may include whether cookies work, whether they are saved at a scheduled time, and whether refreshing affects cookies.

4. Design Language Test: Differences in web design language versions can cause serious problems on the client or server side, such as the html version used. This issue is especially important when developers are not working together in a distributed environment. In addition to the HTML Version, different scripting languages, such as Java, JavaScript, ActiveX, VBScript, and Perl, must also be verified.

5. Database testing: In web application technology, Databases play an important role. databases provide space for the management, operation, query, and implementation of user requests for data storage of Web application systems. In Web applications, the most common database type is relational database. You can use SQL to process information.

In a web application system that uses databases, two types of errors may occur: 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 program design problems, you can perform tests separately.