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

Hello, everyone. I'm National Day holiday.

Remember the test classification diagram in our previous article? Some of them are "divided by software development phase". It doesn't matter if I don't remember. I took a screenshot here and let's look at the picture directly.

This picture is what we are going to explain in this article. Mainly focus on what they are, what stage of work, test objects, testers, test basis, test methods, test content and so on. Take good notes.

As shown in the figure, "divided by software development phase" into the following seven tests, as the name implies, the subsequent seven tests are carried out at all stages of software development. Do different tests at different stages.

Unit test Unit Testing

Also known as module testing, it refers to the inspection and verification of the smallest testable unit in the software. Is to test the code.

Testing phase: after coding

Test object: minimum module

Tester: development engineer

Test basis: code + detailed design documentation

Test method: White box test

Testing purpose: to verify the correctness of the basic components of the software.

Test content: module interface test, local data structure test, path test, error handling test, boundary test

You can understand this part.

Integration testing (Integration Testing)

Also known as joint testing, assembly testing, on the basis of unit testing, all modules are assembled in accordance with the requirements of the summary design specification and the detailed design specification. The testing work of testing the correctness of the interface of the system and the functions after integration / assembly.

Testing phase: after the unit test

Test objects: interfaces between modules

Tester: White Box / Senior Test engineer

Test basis: module of unit test + summary design document + detailed design specification

Test method: the combination of black box test and white / gray box test

Testing purpose: mainly to check the correctness of the interface between software units, but also to check the correctness of the integrated function.

Test content: data transmission between modules, functional conflicts between modules, functional correctness of module assembly, global data structure, impact of single module defects on the system

System testing (System Testing)

It includes testing the function, performance and the software and hardware environment in which the software runs, focusing on the business point of view, mainly to verify whether the system meets the requirements.

Testing phase: after the integration test passes

Test object: the whole system (software and hardware)

Tester: black Box / Primary and Intermediate Test engineer

Test basis: requirement specification

Test method: black box test

Test purpose: to verify whether the system meets the requirements

Test content: business logic (function), interface, compatibility, ease of use, installation, documentation, performance, stability, security, etc.

Acceptance testing (Acceptance Testing)

Is the last test operation before deploying the software. It is the last phase of technical testing, also known as delivery testing. The purpose of acceptance testing is to ensure that the software is ready and that end users can use it to perform the established functions and tasks of the software.

Testing phase: after the system test passes

Test object: the whole system (software and hardware)

Tester: system user (tester + customer representative, or customer related staff)

Test basis: requirement specification + task statement

Test method: black box test

Test purpose: to determine whether the product can meet the requirements specified by the contract or the user

Test content: same system test

Regression test (Regression Testing)

It means that after modifying the old code, retest to confirm that the problem has been fixed and that no new errors have been introduced.

Testing phase: multiple regression tests are performed at all stages of software development

Test object: some test cases of the corresponding bug and related modules

Testers: relevant testers (each phase of regression testing corresponds to each stage of the tester)

Test basis: bug description + evidence for testing at all stages of software development

Test method: the corresponding test method in each stage of software development

Test purpose: retest to make sure that the changes do not introduce new errors or cause errors in other code

Test content: the corresponding bug description content and some test cases of related modules (unlimited)

Alpha Test (Alpha Testing)

Alpha test, also known as alpha test, is an informal acceptance test, which is carried out by a user or a user within the company in a simulated production environment. The purpose of alpha testing is to evaluate the FLURPS (function, localization, availability, reliability, performance and support) of software products.

Test phase: after all the above tests have passed

Test object: the core business process of the whole system (software and hardware)

Testers: the actual users of the software (relevant customer representatives) or internal users of the company should generally be the actual users of the software.

Test basis: requirement specification + agreed acceptance standard (it is the acceptance standard to communicate with the customer at the beginning of the project and reach the same result, if not, judge according to the requirement specification standard)

Test method: the method is unlimited (white-box test or black-box test is possible)

Test purpose: evaluate the FLURPS (function, localization, availability, reliability, performance and support) of software products

Test content: a subset or a full set of all the contents of the above tests

Beta test

Also known as beta testing, user acceptance testing is also a kind of acceptance testing, which is carried out by the end users of the software in one or more customer sites.

Testing phase: the beta test can only be started when the alpha test reaches a certain degree of reliability.

Test object: the whole system (software and hardware) is completely decided by the relevant responsible person (tester)

Testers: actual users of the software

Test basis: requirement specification + agreed acceptance standard

Test method: the method is unlimited, and the same as the test object, it is decided by the relevant responsible person (tester)

Testing purpose: beta testing mainly measures the FLURPS of the product, focusing on the support of the product, including documentation, customer training and supporting product production capacity.

Test content: it is entirely decided by the relevant responsible person (tester)

Let's briefly introduce the difference between alpha test and beta test:

First of all, these two tests are generally only available in large general-purpose software, and they are the final stage of testing before the software is launched / released.

Testing sites are different: Alpha testing refers to inviting users to the developer's site to test, while Beta testing refers to testing conducted in the location of one or more users.

The test environment is different: the environment of Alpha testing is controlled by the developer, the number of users is relatively small, and the time is more concentrated. The environment of Beta testing is not controlled by the developer, the number of users is relatively large, and the time is not concentrated.

The execution time is different: the Alpha test is executed before the Beta test, and the Beta test needs to be executed when the Alpha test reaches a certain degree of reliability.

Summary: the above we talked about a total of 7 kinds of testing, then for the primary testing, I think unit testing and Alpha, Beta testing you only need to do a simple understanding; the other four kinds of integration testing, system testing, regression testing, acceptance testing are the top priority, need to be mastered and understood.

In order to make it easier for you to understand, I will give you an example with "mobile phone".

After a series of tests before leaving the factory, I choose several representative ones to let you feel that you can think about how to correspond to the above content one by one in the process of reading.

Integration testing:

Plug and unplug test of the charger, whether the charger can be plugged in, whether it can be charged normally after being plugged in, whether it shows no power after being unplugged, and so on.

Volume increase and decrease switch test: press the increment key to increase the volume; press the decrement key to decrease the volume.

Camera detection: check whether the camera is working properly, and the pixels are consistent with the description

System testing:

All the keys on the interface are tested one by one: whether they are consistent with the instructions

Boot use: beautiful interface, easy to use, operating system compatibility, app use, whether you can set password / fingerprint, etc.

Battery durability testing: detect battery loss, usage, etc., at different temperatures / humidity.

Acceptance test:

The factory organizes a random inspection by the quality inspection department to check whether the mobile phone is consistent with the contract (such as quantity) or the requirement specification (such as quality, size, thickness, function, etc.).

Check one by one with the contract or requirement statement by the customer representative.

The national quality inspection department carries on the test to see whether it is qualified, etc., and gives the certificate of qualification.

When we buy a mobile phone, we get the mobile phone and use it to check whether it conforms to the product description of the mobile phone, the instructions in the manual, and so on.

Regression test:

Each of the above links encounter problems and rework to the factory or after-sale, and then the "tester" (no matter who is wrong, which link is wrong, then the relevant test responsible person to return) to conduct a second test.

The story is over. Can you match the story with the content of our class?

Integration testing to check the correctness of the interface of the system and the functions after integration / assembly

System testing to determine whether the product function is consistent with the description of the requirements specification.

Regression testing, retesting to make sure that the changes did not introduce new errors or cause errors in other code

Acceptance test to determine whether the product can meet the requirements specified by the contract or the user

All right, that's all for today. Welcome to leave a message to communicate with me.

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.