see a Web test on the Internet, summed up a good, handy to get
original link: http://jjwenle.blog.51cto.com/2993635/1128989
Test Range
1. Functional Testing
1.1 Basic function Module Test
Analyze each function module according to the user requirement instruction manual and the requirement Analysis manual. Test the relevant functions for each function module.
1.2 Web functionality Test
1.2.1 Link Test
What is a link?
A link is a major feature of a Web site, which is the primary means of switching between pages and directing users to some unknown address pages.
Content of the link test:
Test that all links are indeed linked to the page that should be linked, as indicated, and whether the linked pages exist;
Ensure that there are no orphaned pages on the Web site. The so-called orphaned page means that no link points to the page, only the correct URL address is known to access it. Link tests can be done manually or automatically.
Link testing must be done during the integration testing phase, that is, link testing after all page development for the entire Web site has been completed.
The main test site links are normal, including testing the correctness of the link page, whether the page exists, whether there are orphaned pages.
Common testing tools have Xenu (tools to test the correctness of links).
1.2.2 Form Test
What is a form?
Forms are some forms that need to be displayed and filled out online.
The form has some standard operations, such as confirming, saving, submitting, etc.
The main test form is correct and normative, whether it is suitable for the use of common forms of habit.
The main test methods are: Boundary value test, equivalence class test, and Anomaly class test.
1.2.3Cookies Test
What is a cookie?
A cookie is a very small text file that is placed on your hard disk by a Web server. It's essentially like your identity, and it can't be executed like code or used to spread viruses. It can only be used by you and can only be read by the server provided.
The purpose of using cookies:
Help you save time. If you customize the page, or register a product or service. The cookie remembers who you are. The next time you visit, you will be presented with the information you need and will help you fill in any questions you have already answered.
Cookie Testing
Cookies are typically used to store user information and user sequences of operations on certain applications, and when a user accesses an application using cookies, the WEB server sends information about the user and stores that information in the form of a cookie on the client computer, This can be used to create dynamic and custom pages or to store information such as logins.
Test content
Whether the cookies work properly;
Whether the cookies are kept at a predetermined time;
How the refresh affects cookies.
1.2.4 Design Language test
Test whether the version used by the web design language is standardized or unified, and whether the scripting language used is standardized or unified.
The general use of time code to look at the view. Differences in different versions of the Web design language can cause serious problems on the client or server side;
Especially when developing in a distributed environment, where developers are not together, this problem is especially important.
Test language, in addition to the HTML version of the problem, different scripting languages, such as the use of Java, JavaScript, ActiveX, VBScript, or Perl developed applications are also to be validated on different versions.
1.2.5 Database Testing
Data validation
Depending on the business rules, the user input needs to be verified, so that these check functions work correctly.
Conformance errors and output errors for general test data. Data consistency errors are mainly caused by incorrect form information submitted by users, and output errors are mainly caused by network speed or programming problems, which can be tested separately for both cases. And then the data security test, the general use of SQL injection method.
2. Performance Testing
The performance test of the website is very important for the operation of the website, the performance test of the website is mainly from three aspects: Connection speed test, load test and stress test.
2.1 Connection Speed test
The system does not allow users to wait longer, regardless of the user's use of the same method. The purpose of the connection speed test is to ensure that the user's request is responded to within the permitted time.
Test the link speed of the website in response to the user's response time.
2.2 Load Test
Purpose of the load test:
Load tests are designed to measure the performance of a web system at a certain load level to ensure that the web system functions properly within the requirements range. Load testing refers to the testing of some boundary data to measure the performance of the website system at a certain load level, so as to ensure that the website system will work properly in the demand range. The load level is the number of users who have access to the Web system at some point.
Common automated test tools: LoadRunner.
2.3 Pressure test
The tendency of stress testing should be to cause the entire system to crash to test the maximum pressure the system can withstand without a system crash. It is also a test system limitations and failure recovery capabilities, that is, the test site system will not crash, under what circumstances will crash.
The content of the stress test:
Stress testing must apply the following four basic conditions to a WEB service for effective stress testing:
Repetition (repetition); concurrency (Concurrency); magnitude (Magnitude);
Random changes.
Common automated test tools: LoadRunner.
3. Usability testing
Usability/usability tests are generally judged by hand-tested methods.
3.1 Navigation test
What is a navigation test? Between different user interface controls, such as buttons, dialog boxes, lists, and windows;
or between different connection pages,
Navigation describes how a user operates within a page. Content of the navigation test:
Test the navigation ability of the website is good, such as page structure, navigation, menu, connection and so on is good.
Often use the manual to browse the Web page, according to the general user's browsing habits to judge.
In general, this process allows end-users to participate in this test, and the effect will be more pronounced.
is navigation intuitive?
Can the main part of the WEB system be accessed through the home page?
Does the web system require a sitemap, search engine, or other navigator help?
Test the page structure of the web system;
is the navigation bar, menu, and connection style consistent? The various tips are accurate, ensuring that users intuitively know if there is content and where the content is.
It is better to have the end user participate in the navigation test, the effect will be more obvious.
3.2 Graphics Testing
What is a graphical test?
In the Web site, the appropriate pictures and animation can play both the role of advertising, but also to beautify the page function. A Web site's graphics can include pictures, animations, borders, colors, fonts, backgrounds, buttons, and so on. Graphic testing is part of the aesthetic testing of web pages, the general test of whether the graphics have a clear purpose, and whether the page style consistent, but also with the size and format of the picture test.
The content of the graphics test:
(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. Picture size should be as small as possible, and to be able to clearly explain something.
(2) Verify that all page font styles are consistent.
(3) The background color should match the font color and foreground color.
(4) The size and quality of the image is also a very important factor, generally using JPG or GIF compression.
Manual testing is often used.
3.3 Content Testing
Content testing is used to verify the correctness, accuracy, and relevance of information provided by Web site systems. If the text title matches the text content, there is no need for text.
Often use the interface to browse the way.
3.4 Overall Interface Testing
Test the entire Site system page structure design is consistent with user requirements specification, whether to give users a sense of the whole.
Usually use the interface to browse the way, preferably with end-user participation.
For example, when a user browses a Web site, you should consider
Do you feel comfortable?
Is it intuitive to know where to find the information?
is the design style consistent across the Web application system?
4. Security Testing
4.1 Login Verification
Now the site system basically uses the first registration, after landing the way. Therefore, you must test the valid and invalid user name and password, to notice whether the case is sensitive, how many times you can try the limit, whether you can browse a page without landing and so on.
4.2 Buffer Overflow
An overflow attack is an attack that takes advantage of a buffer overflow vulnerability by controlling the computer's sequence of instructions through overflow, allowing the computer to execute its own malicious code. Buffer overflow is a very common, very dangerous vulnerability.
4.3 log files
In order to ensure the security of the website system, log files are critical. You need to test whether the relevant information is written into the log file and is traceable.
4.4 Security Vulnerabilities
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.
4.5 Cross-site scripting attacks (XSS)
A cross-site scripting attack is an attacker who writes malicious script to exploit a website vulnerability to maliciously steal information from a user.
4.6 Catalog Test
4.7 SSL Socket Test
5. Configuration and compatibility testing
5.1 Platform Testing
Test the site with a different operating system platform.
There are many different types of operating systems on the market, most commonly windows, Unix, Macintosh, Linux, and so on. Which operating system is used by the end user of the Web site depends on the configuration of the user's system.
Platform testing is about testing compatibility issues:
The same application may run correctly under some operating systems, but may fail under another operating system.
Therefore, before the Web system is published, the web system needs to be tested for compatibility under various operating systems.
5.2 Browser Testing
Use a different browser to test your Web site to see compatibility issues with your site in different browsers.
Browsers are the core software of Web system clients, and browsers from different vendors have different support for Java, JavaScript, ActiveX, plug-ins, or different HTML.
In addition, the frame and hierarchy styles are displayed differently in different browsers, and not even displayed at all. Different browsers do not have the same settings for security and Java.
5.3 Resolution Test
Adjust the resolution of the screen to see how the site displays at different resolutions, such as when the interface text is too large when the resolution is low, and some text is too small when the resolution is high.
Page layout in 640x400, 600x800, or 1024x768
is the display normal in resolution mode?
5.4 Connection Rate test
If this is the case, it takes 10 minutes for the user to download a page using a 28.8k modem, but the tester uses the T1 line when testing?
When users download articles or presentations, they may wait for a long time, but they will not be patiently waiting for the page to appear.
5.5 Combination Test
600x800 's resolution may be good on Mac, but it's hard to see on IBM compatible machines.
Using Netscape on an IBM machine can be displayed normally, but it cannot be browsed using lynx.
If all people use the T1 line, you may not need to test the download, upload.
In some internal applications, the development department may declare in system requirements that it does not support some systems and only those that have been set up.
Ideally, the system can run on all machines.
Four. Related Specifications
1. Document Management Specification
2. Related Management Tools (Note: This article is an article on the online test process, supplemented by a detailed description of some parts, thank you in this article for the beginning) related articles
- Global testing under the Web [reprint]
- Design of interface test case in Web test
- Main Jet Web test
- Web Test Induction
- Tool comparison _ Simulate slow speed environment
Web Test Scope
