Software engineering Theory Read NOTE 3

One of the most interesting chapters in this book is software testing, because during the winter vacation I helped my neighbor test his software run, I used his design software, and then asked questions, when my question was put forward, then put forward what should be done the user will be more convenient, feeling a special sense of accomplishment. Once thought the software tester is to regard oneself as the user, wait after the developer completes the procedure to use then then raises the question to be possible.

In fact, the tester's work is far from simple, software testing throughout the software development process, including: Unit Test (Module interface test, local data structure test, important execution path test, error processing test, boundary condition test, Unit test method), integration test (top-down integration, bottom-up integration) , validation test, System test, software debugging (Simple debugging method, inductive debugging deduction debugging, backtracking debugging). Looks particularly cumbersome, but I feel that software testing is more suitable for me than software development, in fact, nothing is as simple as you think, only to really do it to understand the actual process.

Software engineering Theory Read NOTE 3