1. What is software testing?
①In order to find defects or errors in the program
②In order to check whether the product meets user needs
③Improve user experience
2. The purpose of software testing?
①The purpose of module testing is to find inconsistencies between the program module and its interface specifications.
②The purpose of the function strategy is to prove that the program fails to meet its external specifications.
The purpose of system testing is to prove that the expected initial goals of the software product are inconsistent
3. The main principles of software testing
① Testing should be entered as soon as possible (it is best to intervene in the requirements analysis stage)
② All tests should be carried out around requirements
③ Complete testing cannot be achieved, and the defects of the program cannot be found. Properly terminate the test
④Documents should be kept and backed up in time during the testing process
⑤The development of own test procedures should be avoided. Due to the limitation of its thinking, the depth and breadth of the test may be insufficient, and it should be handed over to a third-party or professional test to improve the quality of the test
4. Software definition
software = program + data + document
5. Classification of software testing
1) Test phase division: unit test, integration test, system test, acceptance test (formal acceptance test, Alpha internal test, Beta public test)
2) Test technology division: black box test, white box test, gray Box test
3) Division of test objects: dynamic test, static test (document check, UI check, code review)
4) Test method division: manual test, automated test
5) Test content division: functional test, security test, performance test, Interface test
①Load test: find the inflection point of system performance and the maximum effective concurrency value
②Stress test: select the maximum effective concurrency value of the load for long-term operation
6) Other tests: exploratory test, free test (change of test thinking)
①Smoke Test: Test each repaired version to ensure the normal operation of the basic functions
②Regression test: After the development and submission of the version, re-test to confirm that there are no new defects or errors