foreword
Different types of software products have different testing methods and focuses, and the testing process will also be different. For the same type of software products, different companies have different testing procedures. Although the detailed testing steps of different software are different, the most basic testing process they follow is the same.
Analyze test requirements
Before formulating a test plan, testers need to analyze the software requirements in order to have a clear understanding of the software product to be developed, so as to clarify the test object, the scope of the test work, and the focus of the test. When analyzing requirements, some test data can also be obtained, which can be used as the basic basis of the test plan and lay a solid foundation for subsequent tests.
In addition, analyzing and testing requirements is also to test the software requirements to find unreasonable places in the software requirements.
The determined test requirements must be verifiable, and the test requirements must have an observable and measurable result. Requirements that cannot be verified are not test requirements. Test requirements analysis also communicates with customers to clarify some confusion and ensure that testers and customers reach a consensus on the project as soon as possible
Create a test plan
The test plan generally needs to make the following work arrangements.
① Determining the scope of testing: clarify which objects need to be tested and which objects do not need to be tested.
② Formulate test strategy: The test strategy is the most important part of the test plan. It divides the content to be tested into different priorities and determines the focus of the test. Select the test environment and test method (such as manual test , automated test ) according to the characteristics of the test module and test type (such as functional test , performance test ).
③Arrange test resources: Reasonably arrange test resources based on factors such as test difficulty, time, and workload, including personnel allocation and tool configuration.
④Arrange the test progress: Arrange the progress of the test work according to the software development plan and the overall plan of the product, and also consider the changes of various parts of the work. When scheduling work, it's a good idea to allow a buffer time between each test effort to accommodate plan changes.
⑤ Estimation of testing risks: list the uncertain factors that may arise during the testing process, and formulate coping strategies.
design test cases
①Test Case refers to a set of detailed test plan, including test environment, test steps, test data and expected results. Different companies will have different test case templates. Although they are different in style and style, they are essentially the same, and they all include the basic elements of test cases.
②The principle of test case writing is to try to achieve the maximum test coverage with the least test cases.
Execute the test
① Test execution is the process of executing tests according to test cases, which is the most important activity stage of testers.
② When executing the test, it should be carried out according to the priority of the test cases.
③ During the execution of the test, the tester should closely follow the test process, record the defect, form a report, etc. This stage is the most important work stage of the tester.
Write test report
A complete test report must include the following points.
① Introduction: the purpose of writing the test report, explanations of technical terms and reference materials appearing in the report, etc.
②Test Summary: Introduce the project background, test time, test location and test personnel and other information.
③ Test content and execution status: describe the version of the test module, test type, test case design method used and test coverage rate, provide an evaluation conclusion on the test execution process based on the test pass status, and give test execution activities Improvement suggestions for subsequent test execution activities for reference.
④Defect statistics and analysis: count the number and types of defects found in this test, analyze the causes of defects and give suggestions such as avoidance measures, and record residual defects and unresolved problems.
⑤ Test conclusions and suggestions: Make an overall evaluation of the version quality from multiple dimensions such as requirement compliance, functional correctness, and performance indicators, and give specific and clear conclusions.
Summarize
The data in the test report is true, and each conclusion must have an evaluation basis and cannot be subjective.
Finally: The complete software testing video tutorial below has been organized and uploaded, and friends who need it can get it by themselves [Guaranteed 100% free]
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
