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

Today's software testing is increasingly showing this phenomenon:

It is easier to start than to go deep. As a result, the whole industry has become a trend of two-level differentiation, with a large number of experience bases and automated testing tools, the trend of two-level differentiation is becoming more and more serious.

How to control the depth and width of the test in the future?

From the perspective of Huawei, let's take a look at the training model of Huawei's test team.

1. Software design ability: testing is not inferior to research and development, including architecture, design, understanding of requirements, and even at the business level, testing software design thinking can help a product avoid detours.

2. principle analysis and improvement: testing is not just about finding defects, including locating defects, giving R & D guidance, etc., so as to improve the technical ability of the whole team.

3. Test thinking mode: the analysis mode of testers trained repeatedly through root cause analysis not only makes testers understand more related techniques, but also enables students to master a way of doing things through continuous practice, that is, goal decomposition technology.

4. Understand the ways and routines of doing things: in the words of insiders, Huawei's training model is a design model and a way of playing cards according to routines, which includes key paths, technical methods and coping skills.

5. Continuously summarize and turn experience into routines: persist in precipitating group experience into routines, methods, systems and tools (including test instructions, product line testing experience base, software design baseline, etc.)

6. Make good use of data analysis: how to improve effectively, we must know the right direction? How to achieve effective improvement, we must know the effective methods? The inexhaustible part of the testing experience comes from our analysis of product defects, which is an endless treasure trove. Being good at data direction can not only adjust the testing strategy, but also help us to predict problem defects in effective measures. it can also find a way forward for our continuous improvement.

7. Know how to use soldiers and fight: even if the team is not satisfactory, it also knows how to change the overall ability (consciousness, strategy, tactics). It is still the application of design patterns, but design patterns are not dead.

8. Clear the responsibilities of the post and reasonably set up an efficient team: what skills should each post role undertake, what testing methods and techniques should be mastered, and the goal of selection, education, use and retention should be clear

9. Target management and technical experience: the responsibility for the project lies in the overall PBC management, whether it is SOW or test plan, to the extreme (goal unchanged, method changed)

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.