Software Test definition

Software testing is a process or a series of procedures, to confirm that the computer code to complete its functions should be completed, do not perform its actions, the software should be predictable and stable, will not surprise users (whenever testing a program, you should think of a program to add some value, By testing to increase the value of the program, it refers to the test to improve the reliability and quality of Liao program, improve the reliability of the program, is to find and eventually modify the program error.

Mindset: Start by assuming that the program hides the error

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

Software Testing (English: Software testing), describes a process used to promote the correctness, completeness, security, and quality of certified software. In other words, software testing is an audit or comparison process between the actual output and the expected output. The classic definition of software testing is the process of operating the program under prescribed conditions to detect program errors, measure software quality, and assess whether it meets design requirements.

Introduction to Testing

Software testing [is the process of verifying whether it meets the required requirements or clarifies the difference between the expected and actual results using manual or automated software.

It is a software process that helps identify the correctness (correctness), complete (completeness), and quality (quality) of the computer software (in whole or in part) that is developed to complete (medium or final version); is SQA (software quality Assurance) is an important subdomain.

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

650) this.width=650; "Src=" http://d.hiphotos.baidu.com/baike/s%3D220/sign=b27a1bed36d3d539c53d08c10a86e927/ D4628535e5dde711eb7f78e5a7efce1b9d166177.jpg "alt=" Software Test "style=" width:220px;height:154px; "/> Software Testing

(1) Testing is the process of executing a program in order to discover errors in the program.

(2) A good test scenario is a test scenario that is most likely to find errors that have not been discovered so far.

(3) Successful testing is the discovery of errors that have not been detected so far.

(4) Testing is not just about finding errors. By analyzing the causes of errors and the trend of errors, the project manager can help them identify defects in the current software development process so as to improve them in time.

(5) This analysis can also help testers to design a targeted test method to improve the efficiency and effectiveness of testing.

(6) It is also valuable to test that no errors are found, and a complete test is a way to measure the quality of the software.

(7) In addition, according to the different testing purposes, there are regression testing, pressure testing, performance testing, respectively, in order to check whether the modification or optimization process caused new problems, the software can reach the processing capacity and whether to achieve the desired processing capacity.

Testing principles

First, the test should be carried out as early as possible, preferably at the demand stage, because the most serious error is that the system can not meet the needs of users.

Second, programmers should avoid checking their own programs, software testing should be the responsibility of third parties.

Third, the design of the test case should take into account the legal input and illegal input and various boundary conditions, in particular, also to create extreme state and unexpected state, such as network abnormal interruption, power outage and so on.

Four, we should pay full attention to the cluster phenomenon in the test.

Five, a confirmation process is performed on the error result. The error usually tested by a, must be confirmed by B. Serious errors can convene a review meeting for discussion and analysis, the test results to be strictly confirmed, whether there is really this problem and the severity of the.

Six, to develop a rigorous test plan. Be sure to make a test plan and be instructive. The test schedule is as loose as possible, and you do not want to complete a high level of testing in a very short period of time.

Seven, save the test plan, test case, error statistics and final analysis report, which is convenient for maintenance.

Test target

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

2. Implement tests to reduce the risk that is found.

3. Determines when the test can end.

4. Consider testing as a standard project during the development of a project.

object to test

1. Program.

2. Data.

3. Document.

Testing process

The first step: Analyze the products/projects to be tested, determine the test strategy, and develop a test plan. The plan was approved and turned to the second step. It is important to determine the correct test strategy and guidelines before starting the test work, which is the basis for the later work. It is only through the analysis of the test objectives and requirements that we can determine the input of the test resources.

Step Two: Design the test case. Design test cases should be based on test requirements and test strategy, the progress of low pressure, should be designed in detail, if the progress, cost pressure is large, you should ensure that the test case coverage to critical testing requirements. The use case was approved and turned to step three.

Step three: If you meet the startup criteria (Entrycriteria), perform the test. Testing is performed primarily by building a test environment and executing test cases. Carry out progress control and project coordination during the test.

Fourth step: Submit the defect. This is done with defect audits and validation.

Fifth step: Eliminate software defects. Typically, the development manager needs to audit the defect and distribute the defect. The programmer modifies the defect that he is responsible for. After the programmer has completed the modification, go to the regression test phase. If the completion criteria (ExitCriteria) is met, the test ends normally.

Sixth step: Write the test report. Analyze the test, summarize the experience and lessons, and change it in the next work.

Software test process management, mainly including software testing is what kind of process, how to evaluate a software testing process, how to perform configuration management and test risk analysis and test cost management.

This article is from the "Small Stop" blog, please be sure to keep this source http://10541556.blog.51cto.com/10531556/1814442

Software Test definition