Where does the security of software testing come from?

Where does it come from to test people's sense of security?

Do you get scared in the test work? A little bit of worry? Or is it the calm in the control? Also or lose?

Sharing is more than just technology and methods, more attention to the growth of the heart and collision! Welcome to share the test life of the little drops! [Email protected]

When I was a new person, whenever I finished a version, will be very afraid of the heart, the test is not enough, there is no measurement of the place, so often very not calm the weekend came over again, although the basic did not find any problems, but still feel like such a review again to ease the test pass. Although after a period of time, gradually become an old hand, but this feeling of insecurity occasionally will be floating on the mind: the eldest brother let me test a I did not play business, I measured or pit residual; the development promised that the change is very small, but I know his code pits me a few times, I don't believe him anymore. Gradually, I understood that the original test was a group of insecure people, which also proved from the other side why the Test team had so many girls.

If the test is characterized by a sense of security: the higher the version quality, the better the test, the greater the security of the test, the higher the security of the test, the more time it takes to build the test, and the greater the ability to control the risk. In general, when a use case is finished, the test passes, as shown in the above example, in many cases, the test case execution is not tested after completion, but need to achieve a certain sense of security

Factors that affect security:

1. Test the familiarity with the business

Very familiar, code and logic are clear--high security

Generally familiar, just called or small version touched-the sense of security

Unfamiliar, not tested or invoked--low security

2. Test the evaluation of development Code quality--the sense of security

Well-commented code, clear logic, complete documentation, rich business experience-high security

Logic Complex/business experience general/lack of documentation or annotations-a sense of security

New/test Module basic process is not through/some low-level bug--and safety

3. Test methods and granularity of use case coverage

Test from function to interface to system layering, covering a variety of scenarios and logical branches-high security

Complete testing of the normal function, covering the main process and some scenarios/covering a variety of scenarios but in the case of piling or simulation – a sense of security

Failed to simulate related scenarios during interface test/test only--Low security

Where does the security of software testing come from?