Use software cycles to illustrate different test usage scenarios

From the common point of view, respectively:

From a feature-based perspective:

1, Unit Testing (units test)

This step is primarily for developers to test the correctness of functions, classes, variables, and so on during the development process.

Ex: a function needs to insert some important data into the database. After you have written this function, test it to verify that: 1) The function correctly brings out the data variables that need to be inserted into the database. 2) The data that is brought out can be inserted correctly into the database to be inserted.

2. Function testing (functional test)

As the name implies is the product of the various functions of verification, according to functional test cases, test-by-item, check whether the product meets the user requirements of the function.

Ex: In a project, there are many functions, there are many methods in each function, we can not determine the correctness of the unit test, so we need a more detailed functional testing process.

3. Integrated testing (Integration test)

Integration testing is based on unit testing, all modules are assembled into subsystems or systems according to detailed design requirements for integration testing. Integration testing focuses on the correctness of the interface between modules and the overall functionality after integration.

Ex: Once the unit tests for each function or function module have been completed, it is necessary to test whether the overall data flow between these functions or modules is correct.

4. Scenario testing (Scene test)

A method of improving the test result by using the scene to describe the function point or business process of the system.

Ex: Why does the scene method describe the whole event so clearly? Because, today's system is basically the event to trigger the control process. Such as: we apply for a project, we need to submit the approval documents, and then by the department manager for approval, after approval by the general manager to final approval, if the department manager audit does not pass, the direct return. The scenario is formed when each event is triggered. The event flow is formed by the different triggering sequences and processing results of the same event. This series of processes we use the scene method can be clearly described clearly.

5. System testing (Systems test)

System testing is to integrate the software, as a part of the computer system, and other parts of the systems, in the actual operating environment of the computer system in a series of rigorous and effective testing to discover the potential problems of software to ensure the normal operation of the system. The purpose of the system testing is to verify whether the final software system meets the user's requirements.

。。。。

Based on the non-functional angle:

1, Stress testing (pressure test)

Stress testing is the test of continuous pressure on the system to obtain the maximum service level that the system can provide by identifying a system bottleneck or a performance point that cannot be received.

Ex: We usually browse the Web, when the Web site under a lot of load, when the response of the system will degenerate or fail.

2. Regression Testing (regression test)

Regression testing is the re-testing of previous tests after a change has occurred to ensure the correctness of the modifications. In theory, a new version of the software will require regression testing to verify that the errors previously discovered and repaired are re-emerging on the new software version.

Ex: The goal of regression testing is to verify that defects that have been previously seen but have been repaired are no longer re-emerging. It is generally referred to as a re-testing of a defect that is known to have been corrected again around the time it originally appeared.

3. Security Testing (Safety test)

The process of testing the product to verify that the product complies with the safety requirements definition and the product quality standards.

EX:1) Improve the safety and quality of it products; 2). Try to find a security issue before release to repair and reduce costs;

3) measure security. 4) Verify that the protection mechanism installed in the system can protect the system in practical application, so that it will not be invaded illegally and not be interfered by various factors.

4. Accessibility testing (accessibility test)

is to test the possibility of using software for people with varying degrees of accessibility. Simply put, it is the test software can be blind, no mouse, presbyopia, color blindness and other disabled persons or some people with disabilities normal use, which also contains a normal person in some cases of temporary obstacles in the case of regular use, such as the arms of infants.

Ex: Testing software for the accessibility of people with disabilities, whether all pages and components can be read out by specific read software, whether full keyboard operation is supported, etc.

5. Compatibility testing (compatibility test)

The compatibility test verifies how dependent the software is on the environment it relies on, including how dependent it is on the hardware platform and how dependent it is on the software platform, that is, the portability of the software that is commonly said.

Ex: The primary purpose of the compatibility test is to be compatible with third-party software to ensure that third-party software works properly and that users are unaffected. Because of the variety of application software and system software has been to a large extent, and can be expected to continue to explode at the rate of growth, data sharing between software and system resource sharing becomes a problem, which is the meaning of the compatibility test. Although compatibility testing does not guarantee full quality, compatibility testing is a necessary step for a project.

Use software cycles to illustrate different test usage scenarios