Software testing is to operate the program under specified conditions to find errors and evaluate software quality.
Purpose of software testing: find software defects, track and correct software defects, verify and correct software defects
Software testing classification:
software testing process: requirements analysis-develop test plans-design test cases-execute tests-submit defects-follow up and repair defects-defects Regression Test-Pass Test-Write Test Report
Function test overview: a simple summary to realize software functions available. Functional testing has nothing to do with how the software is implemented. If the implementation changes, the functional test cases are still available. Test case development can be carried out at the same time as software development, which can save software development time. Most functional test cases can be designed through software use cases.
Demand analysis: Through detailed analysis of test requirements, one can understand the scale, complexity, and possible risks of the entire test. The more detailed and accurate the test requirements, the deeper the understanding of the software under test, the clearer the content of the tasks to be performed, and the more sure to ensure the quality and progress of the test.
Develop a test plan: The test plan of a software project is a document that describes the purpose, scope, method, and focus of software testing. Writing test plan documents for verifying the acceptability of software products is a useful way. The test plan includes: test purpose, scope, environment, plan, personnel and time, and risk analysis.
Design test cases: A test case is a set of test inputs, execution conditions, and expected results designed for a specific purpose. Test cases include: use case number, name, priority, preconditions, operation steps, expected results, actual results, and whether it passes.
Use case review: After the test plan is written, the content may be inaccurate or the test content may be omitted, or the software requirement changes may cause the test scope to increase or decrease, and the content of the test plan is not updated in time, misleading the test executives. The test plan contains many aspects. The writer may be limited by his own test experience and understanding of the software requirements, and software development is a gradual process, so the test plan created initially may be imperfect and need to be updated. It is necessary to adopt a corresponding review mechanism to evaluate the completeness, correctness and feasibility of the test plan.
Perform test: configure the test environment, including the basic software and hardware environment, the system under test environment and initial test data; execute business use cases according to the pre-designed business process; record the test results and problems found during the test; Questions are submitted to the defect tracking system for tracking; various information during the test process is collected, and the test process is analyzed and controlled.
End of test execution: The test plan and test cases are executed, all software defects are dealt with, the test work specified by the test plan and test cases is completed, and the software runs continuously within the specified time without causing crashes, system crashes, and data loss errors. The software was discussed by the "Project Management Team" and believed that it could meet the customer's reasonable quality expectations.
Defect management
Writing test report: a brief introduction to the test, including some statements of the test, test scope, test purpose, etc., mainly a brief introduction to the test situation;
test results and defect analysis: this part mainly summarizes various data and measures, including Measurement and capability evaluation of the testing process, quality measurement and product evaluation of software products;
test conclusions and recommendations: This part mainly reports whether the test is fully executed, whether the test goal is completed, whether the test is passed, etc., and the existence of the system Description of the problem, possible potential defects and follow-up work, suggestions for defect modification and product design;
sometimes the appendix has a defect list, defect level definition standards, test passing standards, etc.
This is the end of the test introduction. The theoretical content may be boring and difficult to understand. In the next section, we will introduce how to become a tester, and what test basics and skills testers need to master. Thank you.