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

Boundary value test

Bug is often generated at the boundary of the range. Here are some test cases.

(1) Test the values of each breakpoint in the range that meet the conditions

(2) add 1 to each breakpoint in the test range.

(3) each breakpoint of the test range minus 1.

(4) Test a minimum value that is much smaller than the range.

(5) Test a value that is much larger than the maximum value range.

Install and uninstall tests

Test case:

(1) the newly developed software should not conflict with the mainstream software in the market.

(2) the validity period of software license needs to be tested.

(3) all options during installation should be intact.

(4) the new version of the software does not conflict with the old version.

(5) installation is not allowed in the old version when a new version has been installed.

(6) all texts related to the software should be deleted when uninstalling the software.

(7) turn off the power during installation and uninstallation, and install and uninstall it again when the power is turned on.

(8) Uninstall cannot impress the use of other software.

(9) Interface Bug should not appear

(10) before installation, the installer needs to check whether the disk space size and installation requirements are not.

(11) at the beginning of the installation, the installer needs to remind the user of all prerequisites

(12) there is a progress bar during installation and uninstallation.

(13) installation and uninstallation steps should not be too troublesome

(14) the system should not be restarted too many times during installation and uninstallation.

(15) the uninstall program should be provided

Form test

Test use case

(1) user name cannot be empty

(2) the email address should not be empty and @ should exist

(3) URL should not be empty

(4) all required items must have a value

(5) submit and cancel keys function normally

(6) check for illegal characters in all text fields

(7) only one radio box is selected at a time in a group of radio boxes.

(8) check of regular expressions

(9) Boundary value check

(10) related item check

Link test

(1) all links should point to the correct page

(2) if the linked page does not exist, a friendly prompt page should be displayed to inform the user

(3) orphaned pages should not exist

(4) the text of each hyperlink should be concise.

(5) external links should be valid

Interface integration testing

(1) need to refer to some similar popular software testing interface, the interface design should not be too different.

(2) all components of the same interface are of the same style, orderly and tidy.

(3) each interface has the same style.

(4) the proper use of colors should not be scattered.

(5) the font and format should be appropriate

(6) prompt message should exist

(7) default options should exist for all optional lists

(8) default focus should exist

(9) default values for form items should exist

(10) the implementation of the function is in line with users' habits.

Window interface test

(1) the size of the open window should be the same as the last time it was opened.

(2) when we close the window, if the hardware is not set to save automatically, and we do not save manually, the prompt message should pop up and ask whether to save.

(3) if the window can be moved, the window cannot be moved to a position that cannot be moved back.

(4) when the window size changes, the relative position size of all components should change.

Menu interface test

(1) for each menu item, characters can only take up one line, not two lines.

(2) if a menu item is pressed and a dialog box pops up, the character of the menu item should be. End

(3) if a menu item is pressed to pop up a submenu, the menu item should end with->

(4) shallow menus are advocated. If there are too many menu items, they should be divided into multiple menus.

(5) in a menu, menus with similar functions should be grouped and split lines should be applied between groups.

(6) for some windows, maximize and minimize buttons should not exist.

Check box / check box test

(1) unusable radio boxes should be grayed out

(2) A set of radio boxes can contain 2-7 radio boxes. If there are more than 7, it is recommended to use a list.

(3) the text used after the check box should be concise.

(4) the text behind the check box of the radio box should not be too similar to cause confusion.

Ultra-long string Bug

(1) enter a very long string (such as 1000 characters) into an input field

(2) press the confirm key such as Save or submit or Ok button

Correct result 1: confirmation activities such as save or submit or OK failed, and the error message indicates that the string is too long

Correct result 2: there is a character input limit in the text field, and users cannot enter more than a certain number of characters.

Defective result 1: save, submit, OK button and other confirmation activities are very slow

Defect result 2: only some characters in the name are prompted after the confirmation activities such as save, submission, ok and so on are finished.

Defect result 3: after saving, submitting, ok and other activities, some functions are abnormal, such as the program runs you, the page disappears, etc.

SQL query statement test

This kind of test is a white-box test.

(1) pay attention to boundary values, including between-and,in, > > =

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.