Foreword:
[The end of the article leaves a lot of benefits for everyone]
The basic process of
software testing Software testing, like software development, is a relatively complex work process. If there are no rules to follow, random testing will inevitably lead to confusion in the testing work. In order to standardize and standardize the test work, and complete the test work quickly, efficiently and with high quality, it is necessary to formulate a complete and specific test process.
Software testing process
Different types of software products are tested in different ways and focus, and the testing process is also different. For the same type of software product, the testing process specified by different companies will be different. Although the detailed testing steps of different software are different, the basic testing process they follow is the same: analyze test requirements - develop test plans - design test cases - execute tests - write test reports. The following is a brief introduction to the basic process of software testing.
(1) Analysis of test requirements
Testers need to analyze the software requirements before formulating a test plan, so as 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 test focus.
When analyzing the test requirements, you can also obtain some test data, which can be used as the basic basis for the test plan and lay a solid foundation for the subsequent tests.
Test requirements analysis is actually testing the software requirements. Testers can find out the unreasonable parts of the software requirements, such as whether the requirements description is complete, accurate and unambiguous, and whether the priority arrangement of requirements is reasonable. Testers generally make a software requirements specification check list based on the software development requirements document, and analyze and verify the software requirements according to each inspection item
. Check and judge item by item according to the inspection items. If the requirements are met, select [Yes]. If the requirements are not met, select [No]. If an inspection item is not applicable, select [NA]. Table 1-3 is just a general software requirement specification check list. In actual testing, appropriate additions, subtractions or modifications should be made according to specific test items.
When analyzing the test requirements, it should be noted that the identified test requirements must be verifiable, and the test requirements must have an observable and measurable result. A requirement that cannot be verified is not a test requirement. 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.
(2) Specify a test plan
The testing work runs through the entire software development life cycle, is a huge and complex work, and needs to formulate a complete and detailed test plan as a guide. The test plan is the navigation map of the entire test work, but it is not static. With the progress of the project or the change of requirements, the test plan will continue to change. Therefore, the formulation of the test plan is a process of continuous adjustment and gradual improvement with the development of the project. .
The test plan generally needs to do the following work arrangements.
①Determine the scope of testing: clarify which objects need to be tested and which objects are not.
②Develop a 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 test focus. Select the test environment and test method (such as manual test, automated test) according to the characteristics of the test module and the test type (such as functional test, performance test).
③ Arrange test resources: Make reasonable arrangements for test resources by measuring test difficulty, time, workload and other factors, including personnel allocation, tool configuration, etc.
④ Arrange the test schedule: 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 each part of the work. When scheduling work, it's a good idea to allow a buffer between test jobs in case of plan changes.
⑤ Estimating test risks: List the uncertain factors that may occur in the process of testing, and formulate coping strategies.
(3) Design test
cases Test case refers to a set of detailed test plans, including test environment, test steps, test data and expected results. Different companies will have different test case templates, and although they differ in style and style, they are essentially the same and all include the basic elements of a test case.
The principle of test case writing is to try to achieve maximum test coverage with the fewest test cases. Common design methods for test cases include equivalence class division, boundary value analysis, causal diagram and decision table method, orthogonal experimental design method, logic coverage method, etc. These design methods will be successively handed over in later chapters.
(4) Execute the test
Executing the test is the process of testing according to the test case, which is the main activity stage of the tester. When executing the test, it should be carried out according to the priority of the test case. The test execution process seems simple, as long as the test work is completed according to the test case, but it is not the case. The number of test cases is very large, testers need to complete the execution of all test cases, each test case may find many defects, testers should make test records and tracking, measure the quality of defects and write defect reports.
When the submitted defect is modified by the developer, the tester needs to perform regression testing. If the system becomes immune to test cases, testers need to write new test cases. Functional testing, performance testing, etc. must be carried out in each stage of unit testing, integration testing, system testing, and acceptance testing. This workload is undoubtedly huge. In addition, testers also need to test documents such as user manuals, installation manuals, instructions for use, etc. Therefore, don't simply think that executing the test is to complete the task step by step. It can be said that this stage is the most important work stage for testers.
(5) Writing test report
The test report summarizes a test activity, summarizes the test process of the project, makes statistics on the test data, and objectively evaluates the test quality of the project. Although the test report templates of different companies are different, the main points of the test report are the same. Generally, the software is briefly introduced first, and then it is explained that this report is a summary of the test process of the product and the test quality. Evaluation.
A complete test report must contain the following points.
Introduction: Describe the purpose of writing the test report, the explanation of the technical terms and reference materials that appear in the report, etc.
Test Summary: Introduce information such as project background, test time, test location and testers.
Test content and implementation: describe the version of the local test module, test type, test case design method used, and test pass coverage, provide evaluation conclusions on the test execution process based on the test pass, and provide improvements in test execution activities Recommendations for reference in subsequent test execution activities.
Defect statistics and analysis: Count the number and types of defects found in this test, analyze the causes of defects, and give suggestions for avoidance measures, and at the same time, record residual defects and solve problems.
Test conclusions and suggestions: Overall evaluation of version quality from multiple dimensions such as requirement compliance, functional correctness, and performance indicators, and give specific and clear conclusions.
The data in the test report is real, and each conclusion must be based on evaluation, and cannot be subjective.
Access and exit of the
test The access to the test refers to the conditions under which the testing work of the current version can be started and the testing work of the current version can be terminated. Different projects and different companies have different test access standards. Below are some common test entry and exit criteria.
The test access criteria are as follows:
(1) After the development and coding are completed, the developer has already performed unit testing in the development environment, that is, the developer has completed the self-test.
(2) The functions specified in the software requirements have been implemented. If not fully implemented, developers provide test coverage.
(3) The test project has passed the basic smoke test, and the functions on the interface have been realized and meet the functions specified in the design.
(4) The code of the tested project conforms to the software coding specification and has passed the review.
(5) The developer submitted the test application and provided the corresponding documentation.
The test results are as follows:
(1) The test items meet customer needs.
(2) All test cases have been reviewed and successfully executed.
(3) The test coverage has reached the requirements.
(4) All defects found are recorded in the defect management system.
(5) The repair rate of primary and secondary errors reaches 100%.
(6) The error repair rate of Level 3 and Level 4 has reached 95%.
(7) All remaining problems have solutions
(8) The function, performance, security, etc. of the test items all meet the requirements.
(9) Complete the system test summary report.
Sometimes, there may be some unexpected situations during the testing process that cause the testing work to be suspended. This suspension is not the end of the test mentioned above, but is abnormal. Circumstances that require a pause during testing include the following.
(1) When the tester found a major defect during the smoke test, the test could not be carried out normally, and it was necessary to suspend and return to the development.
(2) When the tester finds too many bugs during the smoke test, they can apply to suspend the test and return to development.
(3) The test items need to be updated and adjusted and suspended, and the total test performance should be suspended accordingly.
(4) If testers have other tasks with higher priority, they can apply for suspension of testing.
Key point: Learning materials Learning is of course inseparable from materials. Of course, 600G learning materials are also prepared for you here.
If you need it, please pay attention first and then privately. Keyword【000】Get it for free. Note that the keyword is: 000
Doubt: Why pay attention in the first place? Re: Because if you don't pay attention, you can't see it if you send a private message back
Project combat
app projects, banking projects, pharmaceutical projects, e-commerce, finance
Large-scale e-commerce projects
A full set of software testing automation testing teaching video
300G tutorial data download [video tutorial + PPT + project source code]
A complete set of software testing automation testing factory experience
python automated testing ++ full set of templates + performance testing
I heard that the iron juices who follow me and Sanlian have been promoted and raised their wages and become rich! ! ! !