Experience in Software engineering (10)

This chapter of software testing I think that is the follow-up work. The entire large and complex software design, the work is not done, but also need to test the software to verify the security stability of the practicality and so on. The first to test is certainly the system itself has no errors, if the system itself has a problem with the structure of the code, then there is no practical stability.

For a complex software system, the software test should be carried out as early as possible, so as to avoid the chain reaction caused by the previous error, and more errors later. Should try to avoid the programmer to check their own programs, independent testing.

and test as much of the comprehensive data as possible. For example, when we are programming, it is a good idea to enter several different data to verify whether the program is correct or not. Software testing to roughly after unit testing, integration testing, validation testing, system testing and many other links, all confirmed, before it can be considered a complete and correct software system, can be handed over to the user side.

Experience in Software engineering (10)