This week's class software engineering software engineering test were explained, we all know, we often encounter in the programming bug, the bug might be hidden, may also be evident, whether in special circumstances bug or vulnerability under the dominance of the software in order to reproduce, as long as the impact on the user experience or cause the software does not work, then we should fix this loophole. bug in the software are many and varied and can not be avoided, but when we write the code can reduce the occurrence rate bug in our code by improving their skills, the teacher in the classroom in terms of the recent crash of the Boeing 737max examples is to show by Boeing 737 crash, no matter how perfect the test, after all, not a substitute for actual effect, it said, for example, an aircraft component parts of 10W, but if the passing rate of each part is 99.99999% of the words, then the final pass rate of this aircraft is how much? Results of operations we can calculate the probability of the final at almost 30%. Then the analogy into our code, if we correct rate of each line of code is 99%, then write the correct probability 10000 rows and how much? This probability is small, poor. The actual development process, the code once an error occurs, then often takes a lot of time to modify, if this error can not easily be found, then this time you have to turn on repeated. In this case, it is particularly important to test the correctness, as well as software code. Test software, is required to predict errors, so just to find errors in the code, but also recognizes the fundamental error which, in this context, the significance of software testing to show up.
The above is what I say to the teacher first two classes of software testing ideas, the two classes is that the English word experiment before statistics for secondary development, to find a text which is the longest English word Solitaire combination. The course of the experiment, and not so good to do, looked around with a class of students to complete until the second lesson I was hastily completed this process of reflection, why people can imagine 1 lesson is complete and I have to use two. After analyzing feel there should be no reason to store their code base, it is for example in C ++ development process, I accumulated a lot of their code repository, for some specific functions previously only been written from the warehouse to get the code out of use on the line, which can greatly save development time, in this case, I will be available before the code number of projects in the files grouped into a code repository Java development, using the method of preparing the next timing, use this code repository before then in class with two classes in order to develop experimental hastily rewritten again. Because people would be able to complete development on a small lesson, I believe that if you can also do it through their own efforts.
In this week's software engineering, I realized that it is the greatest: along with testing during the development process, a step to a test. In the actual development process of Chinese medicine to understand the accumulation code repository.
Next, I went to the rewriting of a word from the petty Solitaire experimental induction of this code repository when accounting.