Web testing introduces a UI test

With the rapid development of Web 2.0 technology, many companies have developed web-based Web services, often in the design and development of Web applications, it is difficult to simulate a large number of users to access the system at the same time, so when the Web site encountered peak access, The server is prone to slow response times and even service outages. To avoid this, you need a performance test tool that can realistically simulate a large number of users accessing Web applications to test the response time of static HTML pages, and even to test the response time of Dynamic Web pages (including ASP, PHP, JSP, etc.). Provides data basis for server performance tuning and tuning.

Common Web application Procedures :

key Web application test points :

(i) functionality
(ii) Usability
(iii) Browser compatibility
(iv) Security
(v) Load and stress
(vi) Storage and Database

Functional testing. We don't have to say much.

UI Test

The purpose of the UI Test 1 is to ensure that the user interface provides the user with the appropriate access or browsing capabilities by testing the functionality of the object. Ensure that the user interface complies with company or industry standards. Verify user interaction with the software through user interface (UI) testing. The goal of the UI test is to ensure that the user interface provides the user with the appropriate access and browsing capabilities of the test object. In addition, UI testing ensures that objects within the UI function meet expectations and comply with company or industry standards.

Navigation test:

Navigation describes how a user operates within a page, between different user interface controls, such as buttons, dialogs, lists, Windows, and so on, or between different connection pages. You can decide whether a Web application is easy to navigate by considering the following questions: is navigation intuitive? Is the main part of the Web system accessible through the home page? Does the web system require a sitemap, search engine, or other navigational aids? Putting too much information on a page tends to have the opposite effect as expected. Users of Web applications tend to drive the goal and quickly scan a Web application to see if they have the information they need, and if not, they leave quickly. Few users are willing to take the time to familiarize themselves with the structure of the Web application system, so the Web application navigation Help is as accurate as possible.
Another important aspect of navigation is the consistency of the Web application's page structure, navigation, menus, and connection styles. Make sure the user intuitively knows if there is content in the Web application and where the content is. Once the hierarchy of Web application system is decided, it is necessary to test the user navigation function, let the end user participate in this kind of test, the effect will be more obvious.

Examples of test cases are as follows:

form (form) test

Example form:

The test cases are as follows:

UI Test Checklist

Hyperlinks
1. Is the links meaningful?
2. Is there any broken links?
3. Do I internal links work correctly?
4. Do I external links work properly?
5. Is all links to external sites in the website tested?
6. Is images correctly hyperlinked?
7. Can the user navigate using text only?
8. Does every hyperlink exist on the site map?
9. Is the hyperlinks ' colours standard?
Does The link bring the user to the correct Web page?

Tables
11. is the columns wide enough or the text wraps around the rows?
is the row and columns headings of tables appropriate?
is the complex tables broken down into simpler ones, wherever required?
Does The user has to scroll right constantly in order to see the contents in a table?
. is table captions meaningful?

Frames
16. Is every frame associated with a title?
. Can the user resize the frame?
is the frame size appropriate?
Does the horizontal and vertical scrollbar appear wherever required?
Does Any frame handling mechanism exist for browsers Tha does not support frames?

Forms
Keyboard shortcuts provided for movement between different fields of forms?
Does the tabbing feature traverse the appropriate fields in the correct sequence?
Mandatory fields marked clearly?
is descriptive labels for all fields provided?
Information formatted, wherever required (for example,date format could in mm/dd/yyyy)
is error messages meaningful and appropriate?
27.Does the size of the text fields give enough, the user to type?
28.Ared fields used appropriately?
is a information asked more than once in the form? Is the user prevented from entering the same data multiple times?
Does the form include a ' reset ' button to clear its contents?

Text fields,buttons,list boxes,check boxes
31.Do the next fields accept invalid characters and special characters?
Can text be selected using SHIFT + arrow key?
. is the user able to select any combination of options in check boxes?
Can the user select more than one option in radio buttons?
Does the button click Trigger the required action?
Can the user add text in the list boxes?
Can the user add text in the combo boxes?
Required commands and options exist in each menu?
Abbreviations used in list boxes/buttons?
is the label names meaningful?
is mouse actions consistent across Web pages?
is red colour used to highlight active items (many users are colour bind)?
Are all the data inside the List/combo box listed in Chronologica order?
44.Are validation checks for text fields present
45.Do numeric values handle upper and lower range of values appropriately (boundary value analysis)?
Does the navigation button work as required?
Does the text fields accept maximum permissible data?
Can an alphanumeric character is entered in numeric
. is the command buttons disabled when they is not on use?
Are there any spelling or grammatical mistakes in captions or labels?

First here today, I hope you can help the management of software quality. Other articles you might be interested in:

Software Testing Process Reference one
Ten free Web UI test tools
Design ideas of Internet database architecture
Enterprise Application Architecture mode N-tier multi-tier architecture
An enterprise social application network topology architecture diagram
IT Infrastructure planning scenario one (network system planning)
Food chain Company It informatization solution One
Rest Service Introduction
Enterprise Service Bus Introduction

If you want to know more software development, system it integration, Enterprise informatization, project management and other information, please follow my subscription number:

Petter Liu
Source: http://www.cnblogs.com/wintersun/
This article is copyright to the author and the blog Park, Welcome to reprint, but without the consent of the author must retain this paragraph, and in the article page obvious location to the original link, otherwise reserves the right to pursue legal responsibility.
The article was also published in my Independent blog-petter Liu blog.

Web testing introduces a UI test