Web-based system testing Web-based system development, the absence of rigorous process, we in the development, publishing, implementation and maintenance process of the Web, might run into some serious problems, high probability of failure. Moreover, with the Web-based systems become more complex, the failure of a project may lead to many problems. When this happens, we may not be able to save the shaken confidence in the Web and the Internet, causing Web crisis. And, Web crisis may be more severe than the software developer software crisis faced by more extensive.
In the Web engineering process, Web-based system testing, validation and acceptance is an important and challenging task. Web-based system testing different from traditional software testing, it will not only need to check and verify operation in accordance with design requirements, but also to test the suitability of the system in different end users browser display. It is important, but also for the security and usability testing from the end user perspective. However, Internet and Web media unpredictability makes it difficult to test Web-based system. Therefore, we must complex new methods and technologies based on Web system for testing and evaluation. ? General software release cycle of monthly or yearly basis and release cycle of Web applications in days or even in hours.
Web testers have to deal with a shorter release cycle, testers and test managers face the transition from traditional test C / S structure and framework of the rapidly changing environment to test Web applications.
First, functional testing
1, the link test? Web application link is a major feature of the system, and it is to switch some of the major means to guide the user does not know the address of the page between pages. Link test can be divided into three areas. First, test whether all links by as indeed link indicated to the page for the link; Secondly, test the linked page exists; Finally, to ensure that no orphaned pages on the Web application system, the so-called orphaned pages that are not link to the page only know the correct URL address to access. ? Can automatically link test, now there are many tools can be used. Link test must be completed in the integration testing phase, that is to say, to link test after all pages throughout the Web application system developed.
2, form test? When the user to the Web application to submit information system administrator, you need to use a form action, such as user registration, login, and other information submitted. In this case, we have to submit test the integrity of the operation, to verify the accuracy of the information submitted to the server. For example: users fill in the date of birth and occupation is appropriate, fill in the respective provinces and whether the city matching. If you use the default values, but also to test the correctness of default. If the form can only accept certain values specified, then it has to be tested. For example: only accept certain characters, these characters can skip the test to see if the system will complain.
3, Cookies Test? Cookies are usually used to store user information and user applications in an operating system, when a user uses Cookies to access a certain application system, Web server sends information about the user, to the information in the form of Cookies stored on the client computer, which can be used to dynamically create and customize landing pages or store information. ? If the Web application uses the Cookies, Cookies must check whether it can work. Content of the test may include whether Cookies work, whether to save a predetermined time, have any effect on refresh Cookies and so on.
4, language test? Web design language differences can cause problems versions of the client or server side serious, such as the use which version of HTML and so on. When developing in a distributed environment, developers are not together, this issue is particularly important. In addition to the HTML version of the problem, different scripting languages, such as Java, JavaScript,? ActiveX, VBScript or Perl, also have to be verified.
5, database testing? In Web application technologies, play an important role in the database, the database management system for Web applications, operation, query and implement user requests for data storage such as providing space. In Web applications, the most common type of database is a relational database, you can use SQL to process the information. ? Using a Web database application system, under normal circumstances, two errors may occur, namely, data consistency error and output error. Data consistency error was mainly due to the user submits the form information is not correct and caused the output error was mainly due to network speed or programming caused problems for both cases can be tested separately.
Second, the performance test
1, connection speed test
Users connect to the Web application's speed varies depending on the way the Internet, they may be dial-up or broadband Internet access. When downloading a program, the user can wait for a long time, but only if a page would not have access. If the Web system response time is too long (eg more than 5 seconds), because users will not have the patience to wait and leave. ? In addition, some pages restricted overtime, if the response is too slow, the user may not have enough time to browse the content, you need to re-landed. Moreover, the connection is too slow, and may cause loss of data, allowing users to get real page.
2, load testing
Web load test is to measure a load on the system level performance, to ensure that the Web system to work properly within the range of needs. Load level may be at some point the number of users simultaneously accessing Web systems, can also be a number of online data processing. For example: Web applications can allow the number of simultaneous users online? If you exceed this number, What will happen? Web applications can handle a large number of user requests for the same page?
3, stress test
Load testing should be scheduled, tested in a real network environment after the Web publishing system. Because an enterprise internal staff, especially the project team is always limited, and the number of requests a Web system can simultaneously process will be far beyond this limit, therefore, only on the Internet, accept the load test, the result is correct credible. ? Stress testing is the actual destruction of a Web application reflects the system, the test system. Stress testing is to limit the ability to test and fault recovery system, that is, Web application testing system will not collapse, in what circumstances would collapse. Hackers often the wrong data load until the Web application system crash, then gain access when the system is restarted. Stress testing area includes forms, landing pages and other information transmission and so on.
Third, usability testing
? 1, Tests Navigation Navigation embodiment described user operation within a page, between different user interface controls such as buttons, dialog boxes, windows list and the like; or a different connection between pages. By considering the following questions can determine whether a Web application system easy navigation: Navigation whether intuitive? Whether the main part of the system can be accessed through a Web page? Are Web systems need to site map, search engine or other navigation help? ? Put too much on one page of information is often played with the expected opposite effect. Web application users tend to be purpose driven quickly scanning a Web application to see if there is information to meet their needs, and if not, will leave soon. Few users are willing to take the time to become familiar with the structure of Web applications, therefore, Web application system to help navigate accurately as possible. ? Another important aspect of navigation is the Web application's page structure, navigation, menus, whether connected to the same style. To ensure that users intuitively know which Web applications if there are content, content in any place. ? Web application level, once decided, must begin testing the user navigation feature that allows end users to participate in this test, the effect will be more obvious.
2, graphical test? In Web applications, the appropriate images and animations can not only play the role of advertising, but also play a landscaping feature page. A graphical Web application system can include pictures, animations, borders, colors, fonts, backgrounds, buttons and so on.
Graphic content of the test are:
(1) To ensure that there is a clear use of graphics, pictures or animations do not stack together at random, to avoid waste of transmission time. Image size Web application system to be as small as possible, and to be able to clearly explain something, generally linked to a specific page.
(2) verify that all pages of the same style font.
(3) should be matched with the background color and font color and foreground colors.
The size and quality (4) the picture is also a very important factor, generally use the JPG or GIF compression.
3, the content of the test
Content test used to test Web applications provide information correctness, accuracy and relevance. ? Accuracy of the information refers to information that is reliable, or misinformation. For example, the list of commodity prices, error rates may cause financial problems and even lead to legal disputes; accuracy of the information refers to whether there are grammar or spelling errors. Such tests typically use some word processing software to carry out, such as using Microsoft Word's "spelling and grammar check" feature;? Relevance of information means that if you can find a list of information or entry associated with the current view information on the current page, also Web site is general in the so-called "related articles list."
4, the overall interface test
Overall interface refers to the entire Web page design application system, an overall sense to the user. For example: When a user browses the Web application system is comfortable, whether instinctively know where to find the information? Whether the entire Web application system design consistent? ? The overall interface testing process is actually a process of investigation to the end user. Web applications generally take to do a questionnaire form on the home page to get feedback end user. ? All of usability testing, the need of involvement of outsiders (no connection with the Web application development, or contact a few staff), preferably end-user participation.
Fourth, the client compatibility test
1, platform testing
There are many on the market a different operating system types, the most common are Windows, Unix, Macintosh, Linux and so on. Which operating system end-user Web application system actually use, depending on the configuration of the user's system. Thus, compatibility problems may occur, may be able to operate normally in the same application under certain operating system, but in other operating systems might fail. Therefore, prior to Web publishing systems, the need for compatibility testing of Web systems in a variety of operating systems.
2, browser testing
The browser is the core component of the Web client, browser from different vendors for Java ,, JavaScript,? ActiveX,? Plug-ins or a different HTML specifications have different support. For example, ActiveX is Microsoft's product is Internet? Explorer designed, JavaScript is Netscape's products, Java is Sun's product and so on. In addition, the framework and hierarchy of styles in different browsers have different display, or even not at all. Not the same in different browsers and Java security settings. ? One way to test browser compatibility is to create a compatibility matrix. In this matrix, testing different vendors and different versions of the browser suitability for certain components and settings.
Fifth, security testing
Regional security testing Web applications are:
(1) now uses the basic Web applications to register after landing approach. Therefore, we must test valid and invalid user name and password, to note whether the case-sensitive, can try to limit how many times, if you can not login directly browse a page and so on.
If (2) Web applications have a limit overtime, that is, a user login (eg 15 minutes) did not click on any page within a certain period of time, the need to re-login to work properly.