Shulou(Shulou.com)06/03 Report--

Software testing is a process or a series of processes, which is used to confirm that the computer code has completed its supposed functions and does not perform the operations it should not have, and the software should be predictable and stable. It will not bring surprises to users (whenever testing a program, you should think of adding some value to a program, increasing the value of the program through testing, which refers to testing to improve the reliability and quality of the program. Improve the reliability of the program, which means to find and eventually correct the errors of the program.

Mindset: assume from the beginning that there is a hidden error in the program

In short: testing is the process of executing a program to find errors.

Software testing (English: Software Testing) describes a process used to facilitate the identification of the correctness, completeness, security, and quality of software. In other words, software testing is a process of reviewing or comparing the actual output with the expected output. The classical definition of software testing is the process of operating a program under specified conditions to find program errors, measure software quality, and evaluate whether it meets the design requirements.

Brief introduction to testing

Software testing [is the process of using manual operation or automatic operation of the software to verify whether it meets the specified requirements or to clarify the difference between the expected results and the actual results.

It is a software process that helps identify the correctness, completeness, and quality of computer software (whole or part) that has been developed (intermediate or final version); it is an important subdomain of SQA (software quality assurance).

Glenford J.Myers has made the following points about the purpose of software testing:

Software testing

(1) testing is the process of executing a program in order to find errors in the program.

(2) A good test scheme is one that is very likely to find errors that have not been found so far.

(3) A successful test is a test that finds errors that have not been found so far.

(4) testing is not just about finding errors. By analyzing the causes and trends of errors, project managers can help project managers find defects in the current software development process in order to improve them in time.

(5) this kind of analysis can also help testers to design targeted testing methods and improve the efficiency and effectiveness of testing.

(6) testing without errors is also valuable, and complete testing is a method to evaluate the quality of software.

(7) in addition, according to the different testing purposes, there are regression testing, stress testing, performance testing, etc., respectively, in order to check whether the modification or optimization process causes new problems, whether the software can achieve the processing capacity and whether the expected processing capacity is achieved.

Testing principle

First, testing should be carried out as soon as possible, and it is best to intervene in the requirements phase, because the most serious mistake is that the system cannot meet the needs of users.

Second, programmers should avoid checking their own programs, and third parties should be responsible for software testing.

Third, legal and illegal inputs and various boundary conditions should be taken into account when designing test cases, and extreme and unexpected states should be created in special cases, such as abnormal network outages, power outages and so on.

Fourth, full attention should be paid to the clustering phenomenon in the test.

Fifth, there should be a process of confirming the wrong results. Generally speaking, the errors tested by A must be confirmed by B. Serious errors can be discussed and analyzed at a review meeting, and the test results should be strictly confirmed to see if the problem really exists and how serious it is.

Sixth, make a strict test plan. Be sure to make a test plan and be instructive. The test schedule should be as loose as possible, and do not expect to complete a high-level test in a very short time.

Seventh, properly save test plans, test cases, error statistics and final analysis reports to facilitate maintenance.

Test target

1. Find some development risks that can be avoided by testing.

2. Implement tests to reduce the risks found.

3. Determine when the test can be completed.

4. Treat testing as a standard project in the process of developing a project.

Tested object

program.

data.

Documents.

Testing process

The first step: analyze the product / project to be tested, determine the test strategy, and make a test plan. After being reviewed and approved, the plan moved on to the second step. The correct testing strategies and guidelines must be determined before the start of the testing work, which are the basis of the later work. Only by analyzing the test objectives and requirements clearly can we determine the input of test resources.

Step 2: design test cases. The design of test cases should be carried out according to the test requirements and test strategy. When the schedule pressure is small, it should be designed in detail. If the schedule and cost pressure is large, then the test cases should be ensured to cover the key test requirements. After the use case is approved, move on to step 3.

Step 3: if the Startup guidelines (EntryCriteria) are met, then the test is executed. The main purpose of executing the test is to build the test environment and execute the test cases. Progress control, project coordination and other work should be carried out when performing the test.

Step 4: submit defects. Defect audit and verification should be carried out here.

Step 5: eliminate software defects. Typically, the development manager needs to review the defects and assign them. Programmers modify the defects they are responsible for. After the programmer's modification is completed, enter the regression testing phase. If the completion criteria (ExitCriteria) are met, the test ends normally.

Step 6: write a test report. Analyze the test, summarize the experience and lessons of this time, and change it in the next work.

Software testing process management mainly includes what kind of software testing process is, how to evaluate a software testing process, how to carry out configuration management and test risk analysis, as well as test cost management.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.