As we all know, software testing can not find all defects, and all phases of the software development cycle is still possible to inject a defect exists, but there are some flaws are easy to overlook the test, which gives the software leaving a hidden danger or crisis. These easily overlooked defects include:
1, the installation defects
usually set after the completion of the project code, released when the installation package is the last link, and software testers usually at the time of the test, no part of this test carefully, and use cases focus on other features. When the defect is usually installed by copying mode rather than running the installer to install the software testers, the results of the formal installation problem arises, for example, the control does not lead to registration, the registry does not import so on. Delete the absence of attention to the installation folder exists user files, resulting in data loss; use absolute paths; there is no order of installation instructions.
2, the configuration file
some documents written information administrator password and other passwords in ini configuration file, and is plaintext! This is a safety hazard. Further, some installation files XML file, in order to facilitate the writing of Admin password and password in the database file and the intermediate layer connection. As a qualified software testers, these must be checked can use Notepad to open the file. Because, a little common sense and likes to explore the user may obtain information from hackers and become unconscious. Therefore, the profile might become a software security flaw.
3, Web security flaws
now web developers have noticed: go to the website into its internal web pages, directly copy the URL and paste it into another IE window to enter, you can bypass the login accessed directly. Perhaps commercial websites are concerned about this problem, but many industry software is very easy to overlook.
Website security flaws may also be present in the IE pop-up sub-window. Relaxed some design software, sub-pages can also be run on the main page is closed, this is an obvious flaw, but also greatly increased the risk of error.
4, determines the order / logical defect
Time to interface multiple input judgment, very prone to this problem. Chronological determination e.g., determine the length, determines non waited in vain. If the operator only meet a single condition, preservation can not succeed; and then press the screen from top to bottom order meet the 11 conditions, the storage is not a problem. However, changing the order of about input, verification failure. For example, after the meet the 11 conditions, do not save, reverse the above input into illegal input, and then save the results actually can be successful, it is because the original judgment due happened, or check only on a judge's order last statement , so there is no error. This error page JAVASCRIPT in particular should pay attention to the script. Be able to save not guarantee the data is correct, it may cause a system crash or the subsequent data errors. So, when tested, do not follow the normal order of the input, but to upset the apple cart, look at the code if robust, if it is determined that there are no errors on logic. Good code should stand the toss, then this will all be judged at least save, rather than just simply come to the last line of judgment.
5, debugging statements and redundant information
to maintain and upgrade projects to promote this type of system most likely to latent defects. Typical performance is not deleted or shielded debug statements. Unfriendly interface pops up a message, the user will know the truth generating system mistakenly thought there was a serious malfunction, causing distrust of the software. Somewhere there is a current customer does not need redundant buttons and functions is also a defect page. Extra features make the user think that is an additional part to stop the use of additional, predictable results; and extra buttons mislead strong curiosity user operations generate unnecessary errors.
There is also concern parameter settings, the absence of actual data, or developers when debugging unit tests, the habit of self-set and forget to delete, software testers can ignore this part of the test, it may cause the system to affect the release and acceptance of errors at the customer site.
6, non-reproducible fault
staff to participate in new software or a new test to the developers always have to ask, can not reproduce the defect is to be recorded, it is necessary to do? The answer is yes.Testing must be accurately recorded problem occurs, may not reproduce, or to non-software system itself is the problem, however, may be behind these contingencies is regular, these are not recorded, it is impossible to discover these laws. 7 , multi-node reverse circulation defect current software a lot like the use of workflow to drive. Working flow, it is more likely to flow branch. Easy to overlook the test section, it is a multi-node workflow reverse circulation. For example, by not by a process involving two branches, but the reversal of the flow of time, but there may not be returned to another node on the same level of a node to go. Software testing should pay special attention to the design of such use cases. In addition, sometimes the default branch in forward when there is a default value, for example, by default, the saved time to prompt the user whether by, or may be due to operator fatigue and wrong node, causing a rollback. 8, the input box defects tried to paste the data into the input box and not directly enter it? Here the problem may occur. Press Ctrl + V, when the input frame length is automatically cut according to the length of the input size. But with the mouse, cut off might be impaired. Once the tester is to use this method to enter into a Word document, and save time database crash. Some sites landing password **** can copy down, as long as there immediately displayed in plain text on the clipboard. Input box can be said to be the most problematic part of the trouble can be caused by a lot. Dates, numbers, text, etc., all need patience to test. 9 interface layout flaws Once upon a time, a project manager to reflect back to the issue of testing, customers are not satisfied with the interface. The reason is simple, because the Delete button and get very close on the Save button interface. The results of some operations unskilled service personnel, it is easy to mistakenly press. This question is for testing personnel did not expect, so pay attention to close, delete, save and exit from the button, and so the next button. Click the button should be similar to the regular arrangement of distribution.
Interface layout can also occur on the maximize and minimize the window, it is possible to narrow the window when there is no drop-down box or resolution does not match, the user is concerned, this mistake is really very low. Because some users accustomed to the operation, not like a free hand to use the mouse, especially a lot of input interface, therefore, should pay attention to set keyboard shortcuts. Also, pay attention to when you press Tab to locate the focus of the next order, to avoid jumping too flexible and allow the operator was unable to adapt in time to maintain or modify the interface, do not forget to test whether the software developer has no intention to change these shortcuts way and jump sequence.
10, environmental releases and service packs of
theory, which is a problem of compatibility testing should be covered. Some customers like to update the latest version of the software or Microsoft from time to time to play some patches, the problem arises. Sometimes the upgrade is not necessarily a good thing. These issues are best increase the number of use cases at the time of testing, the use of different software versions of the machine to run a race. There is a law of software testing is: You have not ran the place, something always goes wrong. Often heard developers complain, how my machine no problem, your machine will something of it? This configuration can not completely rely on the administrator to solve the problem, environment configuration item is we most easily overlooked.
11, user management and defect
roles and authorization of user management needs a good look, made its testers know that sometimes in order to facilitate the testing, the test users are having a super-user privileges. Moreover, it is easier to ignore this part of the test user management. Often sent to the customer, many test users are not deleted.
In addition, some user interface and password, to end the life of the software have not changed. In one test, software testers found a user to grant superuser privileges, then change the user restricted rights. Use found that users actually no real recovery authority, there is no right on the user management interface. Early preparation user management use cases, do not wait until the end of the test when it is remembered.
12, defect common sense
Logically or statistically speaking, the computer is allowed so treated, but from common sense terms, these can not happen. Such as phone numbers impossible decimal point, the end time can not be greater than the start time, and so on. In addition, common sense should combine operational characteristics to be judged, therefore, developers and testers to pay particular attention to the cultivation of their knowledge and increase understanding of the needs of the details. Not because the blind pursuit of progress and the most simple code to achieve, for the user, these errors may be very ridiculous.
Although we can not be a perfect test software, but we can still improve our software testing. End of each test, sum up the lack of testing, to further improve the use cases. Think about those software defects easily overlooked, can improve the understanding of software testing and improve software quality organization.