Web testing experience
1. Functional Testing
1.1. Link test
Links Web applications are one of the main features, it is to switch between the page and direct users to some of the pages do not know the address of the principal means. Link test can be divided into three areas. First of all, test all links are indeed in accordance with the instructions as the link link to the page; followed, test the page by the existence of links; Finally, to ensure that Web applications do not in isolation on the page, the so-called isolation of the page that there is no link to the page only know the correct URL address to access.
Links can be automatically tested, there are a number of tools can be used. Test link in the integration testing phase must be completed, that is to say, in the entire Web application system to develop after the completion of all the pages link test.
1.2. Form test
When the user application to the Web administrator to submit information, use the form on the required operation, such as user registration, login, and other information submitted. In this case, we must test the operation of the integrity of the author, submitted to the server to check the correctness of the information. For example: users fill in date of birth and occupation whether it is appropriate to fill in their respective provinces and the city is located, etc. Whether or not matching. If you use the default value, but also test the validity of the default value. If the form can only accept certain values specified, then have to be tested. For example: only accept certain characters, you can skip the test of these characters, the system will look error.
1.3.Cookies test
Cookies are usually used to store user information and user applications in a certain operation, the use of Cookies When a user visits a certain application of the system, Web server will be sent information about users, information in order to put the Cookies stored on the client computer This can be used to create dynamic and customized landing page, or information storage.
If the Web application system uses Cookies, we must check whether the normal work of Cookies. Test can include whether the role of Cookies, by Whether or not the time for book preservation, there is what set of Cookies and so on.
1.4. Design of Language Testing
Web design languages can be caused by differences in client or server-side serious problems, such as the use of which version of HTML and so on. When developed in the distributed environment, the developers are not together, this question is particularly important. HTML version of the problem apart from, the different scripting languages, such as Java, JavaScript, ActiveX, VBScript or Perl, also have to verify.
1.5. Database Test
Technology in the Web application, databases play an important role, the database for the management of Web applications, operations, queries and data storage to achieve the user's request to provide space. In Web applications, the most commonly used database type is a relational database, you can use SQL to deal with information.
In the use of the Web database application system, under normal circumstances, two types of errors that may occur, namely, data consistency error and output error. Data consistency error was mainly due to the form the user submitted incorrect information, and the output error was mainly due to the speed of the network or programming caused the problem, for both cases can be tested separately.
2. Performance Test
2.1. Connection speed test
Users connect to Web applications based on the speed of the Internet changes the way that they may be dial-up telephone or broadband Internet access. When downloading a program, the user can wait a long time, but if only to visit such a page would not. If the Web system response time is too long (more than 5 seconds for instance), users will be patient because there is no left.
In addition, some restrictions on the page there is overtime, if the response is too slow, users may not yet had time to browse the contents of required re-landed on. Moreover, the connection speed is too slow, but also may lead to data loss, so that users are not the real page.
2.2. Load testing
Load testing Web systems are measured in order to load at a given performance level up to ensure that the scope of Web system needs to be able to work properly. Load level can be simultaneously a moment to visit the number of Web users can also deal with are the number of online data. For example: Web applications can allow the number of users online simultaneously? If more than the quantity, situation that will arise? Web applications can handle a large number of users request the same page?
2.3. Stress test
Load testing Web systems should be released in the future, in the actual network environment for testing. Since an enterprise-house staff, in particular, the project team members are always limited, and a Web system to handle the request at the same time far in excess of the quantity limit, therefore, only on the Internet, the acceptance of load testing, the result is right credible.
Web browser clients are the core components, from different browser vendors of Java,, JavaScript, ActiveX, plug-ins or the HTML specifications have different levels of support. For example, ActiveX is Microsoft's products, are designed for Internet Explorer's, JavaScript is Netscape's products, Java is Sun's products and so on. In addition, the framework and structural style at different levels of browser also shows that there is different, do not even show. On a different browser and Java security settings are not the same.
Browser compatibility testing of one of the ways is to create a compatibility matrix. In this matrix, testing different manufacturers, different versions of browsers and settings for some of the adaptive component.
5. Safety test
Web application security testing region are:
(1) present the basic use of Web applications to register, after the landing approach. Therefore, we must test valid and invalid user name and password, it should be noted that case-sensitive, you can test the restrictions on the number of times, can not browse directly to a landing page.
(2) Web application systems have restrictions on overtime, that is to say, the user, after landing at a certain period of time (eg 15 minutes) did not click on any page, whether there is a need to re-visit in order to work properly.
(3) in order to guarantee the security of Web applications, and log files are essential. Whether or not the relevant information required to test written into the log file, whether or not traceable.
(4) When using the Secure Sockets when, but also tests whether the encryption right to check the integrity of information.
(5) server-side scripts usually pose a security vulnerability, the vulnerability and hackers often use. Therefore, we should also test has not been authorized, it can not be placed in the server-side script and editing problems.
6. Summary
In this paper, the functionality, performance, availability, client-side compatibility, security and so on to discuss Web-based system testing methods.
Web-based system testing with the traditional software testing both common, and there is a different place, on the software testing has brought new challenges. Web-based system testing not only need to check and verify whether the design requirements in accordance with the operation, but also to evaluate the system under different client user's browser display is appropriate. Is important, but also from the perspective of end-user security and usability testing.
1. Functional Testing
1.1. Link test
Links Web applications are one of the main features, it is to switch between the page and direct users to some of the pages do not know the address of the principal means. Link test can be divided into three areas. First of all, test all links are indeed in accordance with the instructions as the link link to the page; followed, test the page by the existence of links; Finally, to ensure that Web applications do not in isolation on the page, the so-called isolation of the page that there is no link to the page only know the correct URL address to access.
Links can be automatically tested, there are a number of tools can be used. Test link in the integration testing phase must be completed, that is to say, in the entire Web application system to develop after the completion of all the pages link test.
1.2. Form test
When the user application to the Web administrator to submit information, use the form on the required operation, such as user registration, login, and other information submitted. In this case, we must test the operation of the integrity of the author, submitted to the server to check the correctness of the information. For example: users fill in date of birth and occupation whether it is appropriate to fill in their respective provinces and the city is located, etc. Whether or not matching. If you use the default value, but also test the validity of the default value. If the form can only accept certain values specified, then have to be tested. For example: only accept certain characters, you can skip the test of these characters, the system will look error.
1.3.Cookies test
Cookies are usually used to store user information and user applications in a certain operation, the use of Cookies When a user visits a certain application of the system, Web server will be sent information about users, information in order to put the Cookies stored on the client computer This can be used to create dynamic and customized landing page, or information storage.
If the Web application system uses Cookies, we must check whether the normal work of Cookies. Test can include whether the role of Cookies, by Whether or not the time for book preservation, there is what set of Cookies and so on.
1.4. Design of Language Testing
Web design languages can be caused by differences in client or server-side serious problems, such as the use of which version of HTML and so on. When developed in the distributed environment, the developers are not together, this question is particularly important. HTML version of the problem apart from, the different scripting languages, such as Java, JavaScript, ActiveX, VBScript or Perl, also have to verify.
1.5. Database Test
Technology in the Web application, databases play an important role, the database for the management of Web applications, operations, queries and data storage to achieve the user's request to provide space. In Web applications, the most commonly used database type is a relational database, you can use SQL to deal with information.
In the use of the Web database application system, under normal circumstances, two types of errors that may occur, namely, data consistency error and output error. Data consistency error was mainly due to the form the user submitted incorrect information, and the output error was mainly due to the speed of the network or programming caused the problem, for both cases can be tested separately.
2. Performance Test
2.1. Connection speed test
Users connect to Web applications based on the speed of the Internet changes the way that they may be dial-up telephone or broadband Internet access. When downloading a program, the user can wait a long time, but if only to visit such a page would not. If the Web system response time is too long (more than 5 seconds for instance), users will be patient because there is no left.
In addition, some restrictions on the page there is overtime, if the response is too slow, users may not yet had time to browse the contents of required re-landed on. Moreover, the connection speed is too slow, but also may lead to data loss, so that users are not the real page.
2.2. Load testing
Load testing Web systems are measured in order to load at a given performance level up to ensure that the scope of Web system needs to be able to work properly. Load level can be simultaneously a moment to visit the number of Web users can also deal with are the number of online data. For example: Web applications can allow the number of users online simultaneously? If more than the quantity, situation that will arise? Web applications can handle a large number of users request the same page?
2.3. Stress test
Load testing Web systems should be released in the future, in the actual network environment for testing. Since an enterprise-house staff, in particular, the project team members are always limited, and a Web system to handle the request at the same time far in excess of the quantity limit, therefore, only on the Internet, the acceptance of load testing, the result is right credible.
Web browser clients are the core components, from different browser vendors of Java,, JavaScript, ActiveX, plug-ins or the HTML specifications have different levels of support. For example, ActiveX is Microsoft's products, are designed for Internet Explorer's, JavaScript is Netscape's products, Java is Sun's products and so on. In addition, the framework and structural style at different levels of browser also shows that there is different, do not even show. On a different browser and Java security settings are not the same.
Browser compatibility testing of one of the ways is to create a compatibility matrix. In this matrix, testing different manufacturers, different versions of browsers and settings for some of the adaptive component.
5. Safety test
Web application security testing region are:
(1) present the basic use of Web applications to register, after the landing approach. Therefore, we must test valid and invalid user name and password, it should be noted that case-sensitive, you can test the restrictions on the number of times, can not browse directly to a landing page.
(2) Web application systems have restrictions on overtime, that is to say, the user, after landing at a certain period of time (eg 15 minutes) did not click on any page, whether there is a need to re-visit in order to work properly.
(3) in order to guarantee the security of Web applications, and log files are essential. Whether or not the relevant information required to test written into the log file, whether or not traceable.
(4) When using the Secure Sockets when, but also tests whether the encryption right to check the integrity of information.
(5) server-side scripts usually pose a security vulnerability, the vulnerability and hackers often use. Therefore, we should also test has not been authorized, it can not be placed in the server-side script and editing problems.
6. Summary
In this paper, the functionality, performance, availability, client-side compatibility, security and so on to discuss Web-based system testing methods.
Web-based system testing with the traditional software testing both common, and there is a different place, on the software testing has brought new challenges. Web-based system testing not only need to check and verify whether the design requirements in accordance with the operation, but also to evaluate the system under different client user's browser display is appropriate. Is important, but also from the perspective of end-user security and usability testing.