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

Software testing V model

The V model can be divided into the following different stages: requirements analysis, summary design, detailed design, software coding, unit testing, integration testing, system testing, acceptance testing.

Demand analysis

First of all, it is necessary to make clear what the customer needs, what the software needs to look like, and which functions are needed. The key to this point is the understanding and interaction between the analyst and the customer. Analysts are required to accurately describe the functions and implementation methods that customers need to achieve, give analysis results, and write requirements specifications.

Outline design

It mainly refers to the implementation of the architecture, which refers to the building of the architecture, the description of the functions of each module, the connection of the module interface and the realization of data transmission.

Detailed design

Make an in-depth analysis of the modules expressed in the outline design, analyze the combination of each module, etc., this stage requires to reach the pseudo-code level, has described the specific functions and phenomena of the program. Database design instructions need to be included.

Software coding

According to the detailed design of the module menu, programmers write the actual code.

Unit testing

Unit testing is carried out according to the set minimum test unit, mainly to test the program code, in order to ensure that each unit module is compiled correctly, and the specific division of the unit is different from different software according to different units. for example, there are tests specific to modules, as well as tests specific to classes and functions.

Integration testing

After unit testing, each unit is combined into a complete system, which mainly tests the function realization of each module after combination, as well as the success of module interface connection, the correctness of data transmission and so on. Its main purpose is to check whether the interface between software units is correct. According to the integrated test plan, while combining modules or other software units into a system, run the system to analyze whether the system is correct and whether the components are in sync.

System testing

The whole software system is tested as a whole, including the function, performance and the software and hardware environment in which the software runs.

The system test is completed by the black box tester, which mainly tests whether the function of the system meets the requirements in the early stage, and whether the performance of the system meets the requirements in the later stage, whether there are loopholes, and the compatibility in different software and hardware environments. It is mainly based on the "system requirements specification" document.

Acceptance test

It is mainly that when users get the software, at the use site, they will do the corresponding test according to the user's needs and specifications to make sure that the software meets the effect. Including functional confirmation testing, security and reliability testing, ease of use testing, scalability testing, compatibility testing, resource occupancy testing, user documentation acceptance and so on.

α test

Informal acceptance testing, an internal test with the participation of users, testers and developers.

Alpha testing means that the internal staff of software development companies simulate all kinds of users to test the coming software products (called alpha version) in the development environment, trying to find errors and correct them.

The key of alpha testing is to simulate the actual running environment and the user's operation of the software product as realistically as possible and to cover all possible user operation modes as far as possible. A software product that has been adjusted by alpha testing is called beta version.

Beta test

The public test after the internal test is about to be officially released and will be fully handed over to the end user's test.

Beta testing is carried out by multiple users of the software in the actual use environment, and these users return error information to the developer. When testing, developers are usually not at the test site. Therefore, beta testing is a field application of software in an environment beyond the control of developers. In beta testing, users write down all problems encountered, including real and subjective ones, and report them to the developer on a regular basis. Beta testing mainly measures the FLURPS of the product (that is, function, localization, usability, reliability, performance and support), focusing on product support, including documentation, customer training and supporting product production capacity.

Note: neither alpha test nor beta test can be done by programmers and testers.

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.