Principles of software testing

1. Before the test starts, do not imagineProgramNo or no defects found in (software psychology)
2. Test result data should be predicted before the test
3. Avoid testing programs written by yourself as much as possible, adhere to the principle of independent testing, and establish an independent testing organization if necessary
4. Both valid and invalid inputs should be taken into account in test cases.
5. We should not only check whether the program has done what should be done, but also whether it has done what should not be done.
6. Test adequacy
7. Test Validity
8. Keep all test cases
9. Changes to any tested procedures should be retested (regression testing)

######################################## ########################

1. Good-enough: a measure of the input/output ratio.
2. The coverage of the test is guaranteed, but the exhaustive test is impossible.
3. All tests should be traced back to user requirements
4. The earlier the test, the better. The test process should be combined with the development process.
5. Testing Scale from small to large, from unit testing to System Testing
6. To discover errors as much as possible, it should be tested by an independent third party
7. You cannot modify the program for convenience of testing.
8. We should test what the software should do and what the software should not do.