Take you through the whole process and comprehensively understand the software accidents that belong to testing

     accident ？ traffic accident ？ Yes , Yes, the definition of national accident is ： Generally, it refers to the accidental death caused by the party's violation of laws and regulations or negligence 、 disease 、 damage 、 Damage or other serious losses , Car accidents are one of them . But this year I'm not talking about this , I'm talking about software accidents , What is the software accident ？ Some people , May not understand , Then let me say that software accident is a computer professional term , The definition goes like this ： Unrecoverable system failure caused by software error . Irrecoverable ？ This seems a little contradictory , Especially our function of sending , Like coupons , appear Bug, Can be plucked , That's through code repair , That is also called unrecoverable ？ It seems not. , I simply defined myself in a micro way , There are two ：1. Abnormal software functions caused by personal operation errors or personal reasons , Cause problems such as property loss of the company or loss of users ;2. For objective reasons , If the server suddenly breaks , Power failure and other reasons , Cause the software to be unusable or abnormal , Cause problems such as property loss of the company or loss of users ; What I am discussing this time is 1, Subjective .

What are the familiar accidents at present , For example, there is the glory of Kings test Mail event , Ctrip paralyzed door incident , Pinduoduo coupons BUG Events, etc. , Specifically, you Baidu , We all know .

Maybe you will look at it or think , Is this the test pot ？ Don't get excited. , Not necessarily , The project is a team , You are part of the team , Not your pot , We should also take precautions in advance ？ Murphy's law , What should happen will happen , Maybe one day it's the test's turn ？ I just want to show you something in advance , When managing a test team , What can we do about the accident ？ After all, this is still relatively strange to everyone .

I probably sorted it out , The framework of software testing accidents is as follows ：

There are generally two types of test accidents , One is the configuration error of the test environment , Impact ; The second is about the impact of not testing the function ; For the configuration errors in the environment during the test , Such as push function , Once there is a problem, it will have a great impact , Personally, I think the severity of the operation errors of the environment is far greater than the functional problems , So you must pay great attention to this ;

For the timeline , We are mainly divided into Accident prevention , When the accident happened as well as After the accident , These three processes , We follow what happens , After occurrence , Occurrence prevention , That is, the process we first encountered . For when it happens , The parties understand the process , And immediately report to the direct supervisor for filing , If you have experience, just follow the process when the accident occurs , This process , What is required is that the reporting information should be as detailed as possible , The supervisor should Take the initiative Track and report ; After occurrence , Review the accident , Then make a summary and prevention , Remember that the most afraid thing in this process is , After that , Everyone made a list of things to do , In the end, it was not implemented in place , This is very important to implement , Tracking in place , As for the responsibility for the accident, it depends on how the company handles it ; For prevention , There are three aspects , First, we should do a good job in some operational matters, test precautions and responsibilities of employees , These are written , After entering the position , We should inspect the employees , Avoid becoming a form ; the second , We should organize every quarter Review again , Avoid forgetting ; Third, we should formulate the accident handling process , Reporting process ;


Reward and punishment system for accidents , This one , You can say , It's best not to have an accident , Why? , Because there is an accident, it means it's not a good thing , Definitely the company's boss I know , This is not just personal responsibility , In fact, the overall leadership must be jointly and severally liable , For the level of accident , Major accidents can be judged directly , For vague places , It may be necessary to have rules to judge by principles , I suggest , In addition to the configuration of environment operation , For functionality, subjectivity can arise from problems （ If negligent , If there are rules, don't wait ）, severity , Impact on users , The loss brought by the company is defined in most unified ways through management meetings , Separate standards 1,2,3 Grade , Then the corresponding punishment is also linked to these levels , In fact, the heaviest punishment is to leave , Then there may be no performance , The salary increase is gone , The end of the year is over , There is no hope of promotion , The lowest performance at the end of the year , The specific rules are formulated according to your leaders and the company .


above , It's my simple view and practice of test accidents , I hope it will help you in this aspect , If you like, please help me to praise , Share . If you are interested in the videos of test materials related to this subscription number , Can be in Dou The sound On the search “ The test is not normal ”, View relevant videos , You can also focus on V Subscription number ： The test is not normal .