Some things about web-side functional Testing (i)

Before and now the main work is mainly web-based testing, recently more idle, say their own web functional testing some understanding.

As an IT industry personnel, must be more or less added a number of technical exchange groups and so on, I am the same, but in the group and other testers in the process of communication, I found a problem, a lot of experienced testers (here generally refers to a year or so experience), in the test is easy to ignore some basic things,

resulting in a number of problems in the work, here I will be in the work and spare time to learn some of the experience, to share, but also to record their own learning and growth process. Talk not much, go to the point ...

First, functional testing

1.1 Link Test

Link is a very important feature of Web application system, mainly used for switching between pages to guide users to some of the main means of not knowing the address of the page, link testing general attention three points:

1) The link is actually linked to the interface as defined in the link

2) test whether the linked page of the link really exists

3) Ensure that there are no separate pages in the system (i.e. no links, only accessible via the correct URL address)

PS: Here, incidentally, some little knowledge about the protocol, URL full name "Uniform Resource Locator", which means to get the address of an Internet resource, and the URI means "Uniform Resource Identifier", which represents some resources on the Internet.

1.2 form Test

This can also be understood as data landing ; When users submit information to the server on a Web application, they need to use form actions, such as user registration, login, information change, etc.; In this case, we must test the integrity of the submitted information to verify the correctness of the data submitted to the server, Of course, this also involves

To some often rational logic , such as birth date and occupation, whether the working age is appropriate, the location of the city in the region of the match, etc., if set to use the default value, also need to test.

1.3 Navigation Test

as a test, many times to stand in the user's perspective to think, then, as a user, when he visited a Web site or system, how will the operation?

As we all know, most users are purpose-driven, when he visits a website or web system, will quickly browse the system, can not find the information to meet their needs, will soon leave, few users are willing to take the time to familiarize with the structure of the system, so the navigation test is very important.

The so-called navigation test, that is, between different page jumps, or buttons, dialogs, lists, and windows, by considering these factors, to determine whether an application system is easy to navigate: Is it intuitive? Can the main modules of the system be accessed or reached via the homepage? Does the site need any other help such as a map or search engine in the station?

Another focus of web system navigation is the consistency of page structure, navigation, menus, styles, and so on, ensuring that users can find what they want with intuition or simple judgment.

1.4 Graphics Testing

It can also be understood as UI testing, which includes pictures, animations, borders, colors, fonts, backgrounds, buttons, and so on.

One of the few priorities to consider, I made a rough summary:

1) The picture should have the clear use, represents; picture size as small as possible, generally using JPG or GIF compression

2) The overall style of the page is consistent with the use of the system

3) background color, font, collocation is reasonable

1.5 Content Testing

This is primarily used to detect the accuracy and relevance of information provided by Web systems.

For example: The price of the goods, the description of the text, the accuracy of the information, whether there is a spelling error, the relevance of the information, such as "related articles list, video list, etc." in many websites

1.6 Overall Interface testing

This is what we often call the user experience. Whether users feel comfortable when browsing, overall style, etc.

This I suggest generally do a similar questionnaire survey form, to determine the user's feedback information, preferably with end-user participation

Second, compatibility test

2.1 Platform Compatible

Now there are a lot of operating systems, such as Windows, Unix, Linux, Macintosh, etc., which system users use depends on the user, so the System compatibility test is necessary.

2.2 Browser compatible

Browser is the most core component of Web client, different browser, JAVA,JAVASCRIPT,CSS or HTML specifications have different support, in addition, the framework and structure of the use of different browsers also have different display or not display, Different browsers have different settings for security.

Test browser compatibility, one way is to create a compatibility matrix to test different vendors different versions of the browser compatibility.

For example, test ie, you can use a tool called IETester to test compatibility, or you can switch browser version through the F12 console to test compatibility with previous front-end elements of the display, etc.

In view of a lot of domestic market browser, such as 360, Sogou, Sohu, QQ Browser, and so on, these native browsers are basically using the Internet Explorer core dual-core configuration

Third, safety testing

I do not know much about safety testing, through the data, found that some basic safety knowledge or interoperability, this is to mention it

The main areas of the security test are the following:

1) Now many Web applications are registered after the registration method, therefore, testing the effective invalid user name and password, attention to case sensitivity, the number of times limit, whether you can not login and browse some pages, etc.

2) Whether there is a timeout limit

3) test the user when the relevant confidence is written to the log file, can be traced, etc.

4) If you use a secure socket, you need to test whether the encryption is correct, the integrity of the information before and after encryption, and the correctness

5) Question of whether you can place and edit scripts on the server or front end without authorization

Some things about web-side functional Testing (i)