Java Web tests are divided into 6 parts

1. Function test 2, performance test (including load/pressure test) 3, user interface Test 4, Compatibility Test 5, Safety Test 6, interface test

1 Functional Testing

1.1 Link Test

Link testing can be divided into three areas.

First, test that all links are actually linked to the linked page as described by the link item;

Second, test whether the linked page exists, is correct;

Finally, to ensure that there are no orphaned pages on the Web application system, the so-called orphaned pages are no links to the page, only the correct URL address can be accessed.

Link tests can be automated, and all links are detected through a software test.

Take action: Use the software to automatically detect website links.

Using software:

Xenu Link Sleuth free green installation software

1.2 Form Test

Test whether the form works correctly.

1, the use of the form for online registration, the submit button can work properly, check when the registration is completed should return the success of the message !. Using forms to gather information, the test program can handle the data correctly. You need to verify that the server can save the data correctly, and test that the program running in the background can interpret and use the information correctly.

When the user uses the form for user registration, login, information submission and other operations, test the integrity of the commit operation to verify the correctness of the information submitted to the server. That is, there is no content that should be in the current fill -in project.

For example: The user fills in the birth date and the occupation is appropriate, fills in the province and the city whether matches and so on. If you use the default value, Verify that the default value is correct . When the form can only accept certain values specified, the test does not fill out or select according to the requirements, whether it can automatically error! Prompt for modification. For example, only certain characters can be accepted, and these characters may be skipped during testing to see if the system will make an error.

String length check: Enter content beyond the length of the string to see if the system checks the length of the string for errors.

1.3 Data validation

The system verifies the user input according to the business rules, and tests that the check function works correctly.

For example, punctuation check: The input includes a variety of punctuation marks, especially spaces, various quotes, and enter. See if the system is working correctly.

Information duplication: In some need to name, and the name should be unique information input duplicate name or ID, to see if the system has been processed, will be error, the same name includes whether the case-sensitive, as well as the input before and after the input space, the system to make the correct processing.

Check the deletion function: In some places can delete more than one message at a time, do not select any information, press "delete" to see how the system is handled, will be wrong, then select one and more information, to delete, to see if the correct processing.

Check that additions and modifications are consistent: Check that the requirements for adding and modifying information are consistent, such as adding required items, modifications should also be required, adding items that are defined as integral types, and modifications must be integral. Check the name of the change: Change the name of the item can not be changed to the existing content, see whether the processing, error. At the same time, should also pay attention, will be reported and their name of the wrong.

Repeat the submission form: A record that has been successfully submitted and then submitted to see if the system has been processed. Check the use of the back key situation: in the back of the place, to return to the original page, and then up, repeated several times, see if there will be errors.

Search Check: Enter the contents of the system where there is a search function, and see if the search results are correct. If you can enter more than one search condition, you can add both reasonable and unreasonable conditions to see if the system is working correctly.

Enter information location: Note When you enter information where the cursor is resting, the cursor and the information you enter will be skipped elsewhere.

Upload download file check: Upload the download file function is implemented, upload file can open. What is the format of the uploaded file, whether the system has the explanation information, and check whether the system can do it.

Required fields check: should be filled out when the system is not filled out whether the process has been processed, the required fields are prompted for information, such as the required fields before adding *,

Shortcut key check: whether to support common shortcut keys, such as CTRL + C Ctrl+vbackspace, for some fields that do not allow the input of information, such as the selection of the date on the shortcut is also limited.

Enter check: After the input is finished, press enter directly to see how the system processing, will be error.

When you test a form, there may be some duplication between the test and the form test.

1.4 Cookie Test

What's the matter? Cookies: Cookies are usually used to store user information and the user's operation in an application, and when a user accesses an application using cookies, the Web server sends information about the user and stores the information in the form of a cookie on the client computer. This can be used to create dynamic and custom pages, or to store login information.

The content of the test may include whether the cookie is working, whether it is saved at the scheduled time, and what effect the refresh has on cookies. If the registration information is stored in a cookie, make sure that the cookie works and that the information has been encrypted. If a cookie is used to count the number of times, the number of validations needs to accumulate correctly. Need to communicate with the Guangdong part.

1.5 Database Testing

Test the database with the main test two aspects: Data consistency errors and output errors, respectively. 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.

1.6 Application-specific feature requirements

Try all the actions that the user may have, and try to implement all the features that are required in the document.

1.7 Correlation check: deleting/Adding an item will have an impact on other items, and if so, whether the effects are correct.

2 Performance Testing

2.1 Connection Speed Test

Some pages have a timeout limit, and if the response is too slow, the user may not be able to browse the content before they need to log in again. Moreover, the connection speed is too slow, may also cause the data loss, causes the user to get the real page.

Test the page with a supermarket limit and publish the time-out. Observe whether the logon failure caused by the timeout causes an unrecoverable error.

2.2 Load Test 2.3 pressure test

Instant access Spikes

Send large amounts of data per user

Long-time Use

2.2 2.3 These two types of tests are temporarily unavailable.

3 User Interface Testing

3.1 UI test to see whether the page is beautiful (including the layout of the page is reasonable, the length of the page is reasonable, whether the foreground and background color collocation, the page style is uniform, whether the tone is suitable for human eyes, will be too dazzling, the font size is appropriate, the color of the font and background color match, Whether the font link will appear to set the strange background color, the font color is not too close to the background color or the gap is too large to be able to see the font or stimulate the visual, click on the link when the picture and font will not create a shift)

Table and DIV test: Whether the Web designer placed too much in a table or div, causing the table or div to elongate, whether the table or DIV is aligned, whether there is a gap in the middle, whether there is a dislocation, if overflow is set in the table or div, whether the contents of the table or div are all visible, There is no case of half-word, if the frame structure is used. Whether the frame structure is reasonable, the width of each row of the table is sufficient, whether there is a folding line

3.2 Graphics Testing

The contents of the graphic test are:

(1) To ensure that the graphics have a clear purpose, the picture or animation can not be cross, toss, overlap and other issues, so as not to waste transmission time. Check the pixel of the page, no more than 72 pixels

(2) Verify that all page font styles are consistent.

(3) The background color should match the font color and foreground color.

(4) Test text wrapping is correct. If the description text points to the picture to the right, make sure the picture appears on the right.

3.3 Content Testing

Content testing is used to verify the correctness, accuracy, and relevance of the information provided on the site.

The correctness of information refers to whether the information is reliable or misinformation. For example, a quote for a website, a telephone

The accuracy of the information refers to whether there are grammatical or spelling errors.

The relevance of information is whether the current page can find a list or portal of information related to the current browsing information.

Make sure that the site does not overdo the use of bold characters, large fonts, and underscores.

3.4 Table Test

You need to verify that the table is set correctly. Whether the entire contents of the table can be displayed properly, whether you need to change the location of the page, or if overflow is required.

3.5 Overall Interface Testing

Long-term testing requires user participation!

4 Compatibility test

4.1 Browser Testing

Test different versions of IE and test the compatibility of browsers with different kernels.

The test tool is ready: IETester.

4.3 Resolution test

Does the page layout appear normal in 640x400, 600x800, or 1024x768 resolution mode? Is the font too small to be browsed? Or is it too big? are text and pictures aligned?

4.4 Printer

Tests whether the entire page is displayed correctly when the page is printed.

5 Safety Testing

The website is about to launch the online banking function, so we need to test the overall security of the website. can be considered later.

5.1 Directory settings

The first step in Web security is to set up the directory correctly. There should be index.html or main.html pages in each directory so that all content in that directory is not displayed.

5.2 SSL

If SSL is used, it should be tested when the user enters or leaves the secure site, please confirm that there is a corresponding prompt message. Is there a connection time limit? What happens after the time limit is exceeded?

5.3 Login

It is necessary to verify that the system prevents illegal username/password logons and is able to log on effectively. Is there a limit to the number of user logins? Do you want to restrict logins from certain IP addresses? If the number of logon failures is 3, enter the correct user name and password at the third logon, can pass authentication, password Select whether there is a rule limit can not login and directly browse a page?

Whether the Web application system has a timeout limit, after the user logged in for a certain period of time (such as 15 minutes) did not click on any page, whether the need to re-login to normal use.

5.4 Log files

In the background, be careful to verify that the server logs are working correctly. Does the log remember all transactions? Log failed registration attempts? Do you want to save it every time the transaction is completed? Record an IP address? Record user name?

6 Interface Test
In many cases, Web sites are not orphaned. Web sites may communicate with external servers, request data, validate data, or submit orders.

6.1 Server Interface
The first interface to test is the interface between the browser and the server. The tester submits the transaction, then looks at the server record and verifies that what is seen on the browser is exactly what happened on the server. Testers can also query the database to verify that the transaction data is saved correctly.
This test can be attributed to the form test and the data validation test in the functional test

6.2 External Interface
Some web systems have external interfaces. For example, online stores may want to validate credit card data in real time to reduce the likelihood of fraudulent behavior. When testing, you use the Web interface to send transactional data that validates valid credit cards, invalid credit cards, and stolen credit cards, respectively. If the store uses only Visa and Mastercard cards, you can try to use the data from the Discover card. (A simple client script can identify the code before committing the transaction, for example, 3 means American express,4 means that visa,5 represents mastercard,6 representing Discover.) Typically, testers need to verify that the software is able to handle all possible messages returned by the external server.
This situation may be reflected in remote meter reading

6.3 Error Handling
The easiest place to be overlooked by the tester is interface error handling. Usually we try to make sure that the system can handle all errors, but it cannot anticipate all possible errors in the system. Try to interrupt the transaction during processing to see what happens? is the order complete? Attempts to interrupt a user's network connection to the server. Try to disconnect the Web server from the credit card authentication server. In these cases, can the system handle these errors correctly? Have you charged the credit card? If the user interrupts the transaction, the customer representative calls the user to confirm the order when the order has been saved and the user does not return to the site confirmation.
Take measures: On the basis of understanding needs, give full play to imagination, as far as possible a comprehensive list of anomalies.

7 Conclusion
Whether you're testing the Internet, an intranet, or an extranet application, Web testing is a more challenging task than non-web testing. Users have high expectations for the quality of Web pages. In many cases, like business functions, pages are used to maintain and develop public relations, so first impressions are very important.

is a very important point of the business knowledge and process is the most important.

Java Web tests are divided into 6 parts