Shulou(Shulou.com)06/03 Report--

I. input box

1. Character input box:

(1) character input box: English full-width, English half-width, numbers, spaces or spaces, the special character "~! @ # ¥% …... & *? [] {}" pay special attention to single quotation marks and & symbols. When it is forbidden to enter special characters directly, use the paste, copy function to try to enter.

(2) length check: minimum length, maximum length, minimum length-1, maximum length + 1, enter super-working characters such as copying the whole article.

(3) Space check: there are spaces between characters, spaces before characters, spaces after characters, spaces before and after characters.

(4) Multi-line text box input: enter newline is allowed, save and then display the format in which the input can be saved, only enter enter newline, check whether it can be saved correctly (if possible, check the save result, if not, check if there is a normal prompt),

(5) Security check: enter special strings (null,NULL, javascript,), input script functions (alert ("abc")), doucment.write ("abc"), hello)

2. Numeric input box:

(1) Boundary values: maximum, minimum, maximum + 1, minimum-1

(2) number of digits: minimum digits, maximum digits, minimum digits-1 maximum digits + 1, enter ultra-long values, enter integers

(3) abnormal values, special characters: enter white space (NULL), space or "~! @ # $% ^ & * () _ + {} | []\:";',. /? :'- = and other characters that may lead to system errors, when it is forbidden to enter special characters directly, try to use paste copy to check whether it can be submitted normally, special functions in word, copy to the input box through the clipboard, page breaks, section breaks similar to the superscripts of formulas, special numeric symbols such as ∑, numbers, ∏, +, -, etc.,

Enter negative integers, negative decimals, fractions, input letters or Chinese characters, decimals (in the case of the first 0 decimal points, multiple decimal points), numbers with the first zero, such as 01,02, whether the scientific counting method supports 1.0E2, full-width and half-width digits, mixed numbers and letters, hexadecimal, octal values, monetary input (several digits after the decimal point are allowed),

(4) Security check: copy cannot be entered directly.

3. Date type input box:

(1) legitimacy check: (enter 0 days, 1 day, 32 days), month input [1, 3, 5, 7, 8, 10, 12], day input [31], month input [4, 6, 9, 11], day input [30] [31], input non-leap year, month input [2], date input [28, 29], input leap year, month input [2], date input [29, 30], month input [0, 1, 12, 13]

(2) abnormal values, special characters: enter blank or NULL, enter ~! @ # ¥%. Characters such as & * () {} [] that may cause system errors

(3) Security check: cannot be entered directly, for copy, is there an error in data verification?

4. Duplicate information: in some information that needs to be named and the name should be unique, enter a duplicate name or ID to see if the system has handled it and whether it will report an error, including whether the duplicate name is case-sensitive, and whether the system handles it correctly by entering spaces before and after the input.

Second, search function

If the query condition is an input box, refer to the test method of the corresponding type of the input box

1. Function realization:

(1) if fuzzy query is supported, whether any character in the search name can be searched

(2) whether longer names can be found

(3) matching conditions that do not exist in the input system.

(4) when the user carries out the query operation, the general situation is that the query condition is not cleared unless the requirement is specified.

2. Combinatorial testing:

(1) whether there is a page error when selecting back and forth between different query conditions (single check box and multi-check box are the most prone to errors)

(2) when testing multiple query conditions, we should pay attention to the combined test of query conditions, and different combinations of tests may report errors.

III. Add and modify functions

1. Special key: (1) whether the Tab key is supported; (2) whether the enter key is supported?

2. Prompt message: (1) whether there is an error prompt where it does not meet the requirements.

3. Uniqueness: (1) whether the field is unique and can be added repeatedly, and whether it can be modified to an existing field (the field includes case sensitivity and entering spaces before and after the input, and after saving, whether the data is really inserted into the database, pay attention to the correctness of the saved data)

4. Data correctness:

(1) modify each edit item on the edit page, click Save, whether it can be saved successfully, and check whether the data you want to associate has been updated.

(2) check the required items (that is, whether the prompt is given and whether the data is still saved in the database after the prompt; whether there is a page number disorder after the prompt, etc.)

(3) whether it can be added continuously (for special cases)

(4) when editing, pay attention to the length limit of editing items, sometimes when adding, but not when editing (pay attention to whether the rules are consistent between adding and modifying)

(5) for the edit box with picture upload function, if the picture is not uploaded, check whether the default picture is displayed when editing the page. If the picture is uploaded, check whether it is displayed as uploading picture.

(6) after adding data after revision, special attention should be paid to whether the data on the query page is updated in time, especially when the data is updated on the home page.

(7) when submitting data, click several times in a row to see if the system will continuously add several pieces of the same data or report an error.

(8) if there is no record in the result list or no record is selected, click the modify button and the system will throw an exception.

IV. Delete function

1. Special key: (1) whether the Tab key is supported; (2) whether the enter key is supported?

2, prompt message: (1) do not select any information, directly click the delete button, whether there is a prompt (2) when deleting a message, there should be a confirmation prompt

3. Data implementation: (1) whether multiple products can be deleted continuously. (2) whether it can be deleted successfully when there is only one piece of data. (3) whether the same data can be added after deleting a piece of data. (4) if the system supports batch deletion, pay attention to whether the deleted information is correct (5) if all are selected, pay attention to whether all the data is deleted (6) when deleting the data Should pay attention to whether the data of the corresponding query page is updated in time (7) if the deleted data is associated with other business data, pay attention to its relevance (such as deleting department information, downstream employees of the department, it should be prompted) (8) if there is no record or no record is selected in the result list, the system will report an error by clicking the delete button.

For example, if a functional module has the most basic functions of adding, deleting, changing and searching, the following tests need to be carried out

Single functional test (add, modify, query, delete)

Increase-- > increase-- > increase (continuously increase test)

Add-- > delete

Add-- > delete-- > add (the newly added content is consistent with the deleted content)

Add-- > modify-- > delete

Modify-- > modify-- > modify (continuous modification test)

Modify-- > add (the newly added content is the same as that before the modification)

Modify-- > delete

Modify-- > delete-- > add (the newly added content is consistent with the deleted content)

Delete-- > delete-- > delete (continuous deletion test)

Registration and login module

1. Registration function:

(1) when registering, set the password to a special version number and check whether an error will be reported when logging in.

(2) after the registration is successful, the page should jump to the home page or the specified page in the login status.

(3) delete the entered information in the registration information and check whether the registration can be successful.

2. Login function:

(1) enter the correct user name and password

(2) enter the correct user name and the wrong password

(3) enter the wrong user name and correct password

(4) enter the wrong user name and password

(5) do not enter user name and password (all spaces)

(6) enter only the user name and the password is empty

(7) user name is empty, only enter password

(8) enter the correct user name and password, but are not case-sensitive

(9) username and password include special characters

(10) enter ultra-long values for username and password

(11) deleted username and password

(12) when logging in, whether the CAPTCHA is updated when the page is refreshed or data is re-entered

6. Upload picture test

1. Function realization:

(1) the file type is correct and the size is appropriate.

(2) the file type is correct and the size is not appropriate.

(3) the file type is wrong and the size is appropriate

(4) File type and size are appropriate. Upload a picture that is in use.

(5) the file type and size are appropriate. Enter the existing image address manually to upload.

(6) File type and size are appropriate. Enter the address of the image that does not exist to upload.

(7) the file type and size are appropriate. Enter the image name to upload.

(8) Click upload without selecting a file to see if a prompt is given.

(9) Select different files several times in a row to see whether the last selected file is uploaded

7. Query result list

1. Function realization:

(1) whether the list and column width are reasonable

(2) whether horizontal scrolling is provided when the list data is too wide.

(3) whether the column name of the list corresponds to the content

(4) whether the column name of each column of the list is clearly described.

(5) whether the list shows all unnecessary columns

(6) Click on a column to sort, whether it will report an error (click to see whether the sorting of each page is correct)

(7) whether an error will be reported if you double-click or click a column of information.

8. Check the return key

1. If a record that has been successfully submitted is returned and then submitted, whether it has been processed or not

2. Check the repeated use of the return key. Where there is a return key, return to the original page many times to see if there will be any errors.

9. Enter key check

1. After entering the result, press enter directly to see how the system handles it and whether it will report an error.

10. Refresh key check

1. In the Web system, use the refresh button to see how the system handles it and whether it will report an error.

11. Direct URL link check

1. In the Web system, enter the URL address of each function page directly in the address bar to see how the system handles it, whether it can be linked directly (anonymously), whether there is permission control, whether it is executed directly, and return to the corresponding result page.

Interface and ease of use testing

1. Whether the style, style and color are in harmony

2. Whether the layout of the interface is neat and coordinated (to ensure that everything is displayed, try not to use scroll bars.

3. Whether the operation of the interface and the description of the title are appropriate (ambiguity in the description, pay attention to whether there are wrong words)

4. Whether the operation is in line with people's routine habits (whether the controls with similar functions are put together to facilitate operation)

5. Whether the prompt interface conforms to the specification (cancel and ok should not be displayed in English, confirmation in Chinese should be displayed, etc.)

6. Whether the controls in the interface are aligned

7. Whether the date control is editable

8. Whether the length of the date control is reasonable, the time can be displayed when it is modified.

9. Whether the column width of the query result list is reasonable and whether the label description is reasonable

10. The query result list is too wide and there is no horizontal scrolling prompt.

For long text, does the text box provide an automatic vertical scroll bar

12. Whether the data entry control is convenient

Whether the Tab key is supported or not, the order of the keys should be organized and do not jump randomly.

14. Is there any relevant hotkey provided

15. Whether the prompt description of the control is correct

16. Whether the module calls are unified, and whether the same module calls the same interface.

17. Whether the controls of the page appear normally when you move the page with the scroll bar

The correct format of the date should be XXXX-XX-XX or XXXX-XX-XX XX:XX:XX

19. Whether the page has extra buttons or tags

Whether the window title or icon is unified with the menu bar

21. Whether the window maximization and minimization can be switched correctly

For normal functions, users can use them without reading the user's manual.

23. Are there any confirmation, deletion and other tips when performing risk operations?

24. Whether the operation sequence is reasonable

25. Correctness check: check whether the form, button, table, header, footer, prompts, spelling and grammar of sentences on the page are correct.

The system should warn and prompt before the user performs the wrong operation.

27, page resolution check, in a variety of resolution browsing system to check system interface friendliness.

28. Rationality check: check whether the page returned by the information is reasonable after doing delete, update, add, cancel, back and other operations.

29. Check whether the localization is passed: the English version should not have Chinese information, and the English translation should be accurate and professional.

XIII. Compatibility testing

Compatibility testing not only refers to the compatibility of the interface under different operating systems or browsers, but also takes compatibility into account in some functional tests.

Including operating system compatibility and application software compatibility, and possibly hardware compatibility

For example, when it comes to ajax, jquery, javascript and other technologies, we should take into account the compatibility of different browsers.

XIV. Link testing

The main purpose is to ensure the usability and correctness of the link, which is also an important aspect of website testing.

You can use specific tools such as XENU for link testing.

1 Navigation test

Navigation describes how users operate within a page, between different user interface controls, such as buttons, dialogs, lists, and windows, or between different connected pages. You can decide whether a Web application is easy to navigate by considering the following questions: is the navigation intuitive? Is the main part of the Web system accessible through the home page? Does the Web system need site maps, search engines, or other navigation assistance?

Putting too much information on a page often has the opposite effect as expected. Users of Web applications tend to be goal-driven, quickly scan a Web application system to see if they have the information to meet their needs, and if not, they will leave quickly. Few users are willing to take the time to familiarize themselves with the structure of Web applications, so Web application navigation helps to be as accurate as possible.

Another important aspect of navigation is whether the page structure, navigation, menu and connection style of the Web application system are consistent. Make sure that users intuitively know whether there is content in the Web application and where the content is.

Once the level of the Web application system is decided, we should begin to test the user navigation function, and let the end users participate in this test, the effect will be more obvious.

2 graphic test

In the Web application system, appropriate pictures and animation can not only play the role of advertising, but also play the function of beautifying the page. The graphics of a Web application system can include pictures, animations, borders, colors, fonts, backgrounds, buttons, etc. The contents of the graphics test are:

(1) make sure that the graphics have a clear purpose, and that pictures or animations are not piled together randomly, so as not to waste transmission time. The picture size of the Web application system should be as small as possible, and to be able to describe something clearly, it is usually linked to a specific page.

(2) verify that the style of fonts on all pages is consistent.

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

(4) the size and quality of the picture is also a very important factor. JPG or GIF compression is generally used, and it is best to reduce the size of the picture to less than 30k.

(5) finally, what needs to be verified is whether the text winding is correct. If the caption points to the picture on the right, make sure that the picture appears on the right. Don't make windows and paragraphs odd or stand alone by using pictures.

Generally speaking, it is a good choice to use a little or as little background as possible. If you want to use a background, it's best to use a monochrome one on the left side of the page along with the navigation bar. In addition, patterns and pictures may distract the user.

15. Business process testing (main functional testing)

The business process generally involves the data of multiple modules, so when testing the business process, we must first ensure the correctness of the function of a single module, and then test the data transferred between each module, which is often prone to problems. When testing, we must design different data for testing.

XVI. Security testing

(1) SQL injection (such as landing page)

(2) XSS cross-site script *: the program or database does not filter or deal with some special characters, resulting in some destructive script statements entered by users can be directly written into the database, the browser will directly execute these script statements, destroying the normal display of the website, or website users' information is stolen, when constructing script statements, it is necessary to ensure the integrity of the script.

[xss_clean] ("abc")

Alter ("abc")

(3) enter some symbols after the URL address and try to keep the dynamic parameters back.

(4) the update of CAPTCHA

(5) the current Web application system basically adopts the way of registering first and then logging in. Therefore, you must test valid and invalid user names and passwords, pay attention to whether they are case-sensitive, how many times you can try, whether you can browse a page without logging in, and so on.

(6) whether the Web application system has a time-out limit, that is, whether the user does not click on any page within a certain period of time (for example, 15 minutes) and needs to log in again in order to use it normally.

(7) in order to ensure the security of Web application system, log files are very important. You need to test whether the relevant information is written to the log file and whether it is traceable.

(8) when using secure sockets, also test whether the encryption is correct and check the integrity of the information.

(9) Server-side scripts often constitute security vulnerabilities, which are often exploited. Therefore, you also need to test the problem that scripts cannot be placed and edited on the server side without authorization.

XVII. Performance testing

1 connection speed test

The speed at which users connect to Web applications varies according to the way they access the Internet. They may dial up by phone or surf the Internet with broadband. When downloading a program, users can wait a long time, but not if they only visit a page. If the response time of the Web system is too long (for example, more than 5 seconds), the user will leave because he or she is impatient.

In addition, some pages have timeout restrictions, and if the response is too slow, users may need to log in again before they have time to browse the content. Moreover, the connection speed is too slow, it may also cause data loss, so that users can not get the real page.

2 load test

The purpose of load testing is to measure the performance of the Web system at a certain load level to ensure that the Web system can work properly within the demand range. The load level can be the number of users accessing the Web system at the same time, or the number of online data processing. For example: how many users can be online at the same time in the Web application system? What will happen if this number is exceeded? Can Web applications handle requests from a large number of users for the same page?

3 pressure test

Load testing should be scheduled to be conducted in the actual network environment after the release of the Web system. Because the staff of an enterprise, especially the staff of the project team, are always limited, and the number of requests that a Web system can handle at the same time will far exceed this limit, the results are correct and reliable only if they are placed on Internet and subjected to load testing.

Stress testing refers to the actual destruction of a Web application system, testing the response of the system. Stress testing is to test the limitations and fault resilience of the system, that is, to test whether the Web application system will crash and under what circumstances. * often provide the wrong data payload until the Web application system crashes, and then gain access when the system restarts.

Stress testing areas include forms, login, and other information transfer pages.

Note:

1. What should load / stress testing focus on?

The test needs to verify whether the system can respond to a large number of users at the same time, when the user transmits a large amount of data, and whether the system can run for a long time. Accessibility is extremely important to users. If users get the message that the system is busy, they may give up and turn to competitors. System detection is not only to enable users to access the site normally, in many cases, there may be attempts to send a large number of packets to the server. For security reasons, testers should know what measures need to be taken when the system is overloaded, rather than simply improving system performance.

1) instantaneous access peak

If your site is used to announce the results of the lottery, it is best to make the system respond to millions of requests within a period of time after the winning number is announced. Load testing tools can simulate X users to access the test site at the same time.

2) each user transmits a large amount of data

Most users of online bookstores may only order 1-5 books, but college bookstores may order 5000 textbooks on psychological introductions. Or a grandmother who buys Christmas presents for her 50 children and grandchildren (of course, each child has his or her own email address) can the system handle a large amount of data from a single user?

3) long-term use

If the site is used to process flower orders, then at least hope that it will continue to run for a week before Mother's Day. If the site provides web-based email services, it is best to run the site for months or even years. You may need to use automated test tools to complete this type of testing because it is difficult to do these tests manually. You can imagine organizing 100 people to click on a site at the same time. But organize 100000 people at the same time. Usually, when the test tool is used for the second time, it creates enough benefits to cover the cost. Also, after the test tool is installed, when you use it again, just a few clicks.

Take measures: use performance testing tools such as WAS and ACT,LR to assist in testing

XVIII. Other situations that should be paid attention to in the test

1. When testing, the network-related steps or modules must take into account the disconnection of the network.

2. Each page has a corresponding Title, which cannot be empty, or "untitled page" is displayed.

3. When testing, we should consider whether the page is normal when the scroll bar appears and scrolls up and down.

4. URL is case-insensitive and case-insensitive.

5. For e-commerce sites, when the number of concurrent purchases by users is greater than the quantity of inventory, how does the system deal with it?

6. Avoid simply entering "123", "abc" and so on, so as to make the test data as close to the reality as possible.

7. When testing, try not to use Super Admin for testing, but with new users for testing. Testers try not to use the same user for testing.

8. Prompt message: whether the prompt information is complete, correct and detailed

9. Help information: whether to provide help information, the expression of help information (page text, tips, help files), whether the help information is correct and detailed

10. Scalability: whether there is room for upgrade and whether the interface is retained

11. Stability: hardware and software configuration required for operation, resource occupation, fault tolerance in the event of problems, and data protection

12. Running speed: speed of running, bandwidth usage

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.