Analysis of testing resources and testing risk in software testing

1. Test resource analysis

Different test tasks correspond to different resource requirements. When designing test cases, test engineers need to refer to and apply product backlogs, requirements outlines, user stories, Sprint plans and other documents.

 

When setting up a test environment, you need to obtain software and hardware resources to support the operation of the product; when implementing test management, you need to purchase or use an open source project management platform. When technical skills are insufficient, you need to participate in skills training or even raise recruitment requirements.

 

Before testing activities, test engineers must ensure that the required testing resources are in place, otherwise the testing activities may not be carried out as scheduled.

 

2. Test risk analysis

There are almost all risks in software design and development. Risk is understood as the possibility of certain adverse events, dangers, or activities that may harm related affairs, and the possible adverse consequences. Risks may or may not occur, which is a potential problem.

 

All software development activities have different levels of risk. The level of risk depends on the occurrence of uncertain events, the likelihood of danger, and the severity of the impact.

 

The possible risks in the testing process usually come from three types: project risk, product risk, and external cause risk.

 

01. Project risk

A project usually has a clear main body of demand, and the customer provides specific requirements, and the software company undertakes R&D tasks. Therefore, the demand risk is less. The specific risks come from the following aspects:

 

(1) Team organization factors

The personal quality factor of agile development team members is very important. Even if an inappropriate person is under an efficient process and an excellent team, it is impossible to carry out high-quality software quality assurance activities. Therefore, human risks need to be paid first attention to. Insufficient personnel, insufficient skills, and insufficient training are all potential risks.

 

In addition to the personal quality risks of team members, team communication and procedures are also potential risks. The communication between test engineers and requirements development, program development, and project operation and maintenance is not smooth, the review process is flawed, the value of test activities is insufficient, and the follow-up of defects is not effective. The same is a potential risk.

 

(2) Technical factors

From the perspective of software R&D technology, common problems are requirements research and development issues, and requirements that cannot be correctly and accurately defined are an important factor in most software R&D failures.

 

The second is the mastery of development technical skills, whether there is technical precipitation, whether there is a standardized design review process.

 

From the perspective of software testing, the test environment cannot truly simulate the actual production environment, or the lack of environmental resources preparation are potential risks.

 

Low-quality software requirements development, architecture design, coding and test design, test execution, unfinished data preparation, environmental protection, etc. are also potential risks.

 

(3) Supplier

Nowadays, many software systems are completed by multi-company and multi-team cooperation. Taking the Sichuan Tobacco Center Operation Platform Project as an example, five suppliers jointly undertake the construction of the center’s information platform. Therefore, in addition to team organization and technical factors, suppliers Cooperation with suppliers can also be a project risk.

 

02. Product risk

In addition to project risks, test engineers need to consider product risks based on the characteristics of the test object when implementing test activities. The difference between a product and a project is that product demand often comes from unspecified users, and there is no clear demand subject. Market researchers usually extract demands based on potential demand customers.

 

One of the most common factors of product risk is demand. Inaccurate positioning of market demand and insufficient user demand research often lead to the final failure of the product.

 

In addition to requirements, software products complying with laws and regulations and potential users' application habits are also important risk sources.

 

At the initial stage of testing activities, testing risk analysis is required, integrating the wisdom of testing engineers, identifying risks, and formulating risk prevention and response measures to improve the quality of testing activities.

 

03. External risk

In addition to the risks of customers or suppliers themselves, external risks are not easy to ignore, such as government supervision and natural disasters.

 

To identify the corresponding risk, the test engineer needs to predict in advance and give reliable solutions based on the risk in order to deal with the problems that may arise during the implementation of the test activity.

 

Guess you like

Origin blog.csdn.net/weixin_43802541/article/details/111563518