Test tools are used, and no effective test is carried out, and it is effective to test. First of all, the code must have a good measuring, class or module is low coupling, the responsibility is clear, in order to be tested, otherwise it will not have a good test program, and the test results are not reached. Second, the test code is not easy to write, and there is enough coverage to test all the responsibilities of the class or module. However, it is generally not tested for each particular implementation, because the development of the realization details will be large, thereby bringing a lot of workload, and the test should be targeted for relatively stable things, ie, or modules. The benefits of developing test scripts after the test script 1. By testing scripts will force you to first figure out the responsibility of the class or module, otherwise you don't know what to measure. First write test scripts You can stand on the class or module user's perspective, so that the code is more easy to use 3. When you write a test script, you don't know the details, so your attention is to place the class or module.
