Shout out for domestic software quality: "2021 Domestic Quality Survey Report" released

In 2020 , the "Software Quality Report" official account and Tencent WeTest, Thoughtworks and other communities launched the first domestic software quality survey , which received enthusiastic attention and support from everyone, and released a survey report, which was also praised and affirmed by everyone. The 100 golden sentences  were sent out as an article on the official account, which aroused great attention and resonance from everyone, with more than 10,000 views and a lot of comments.

The survey in 2021 was supported by more communities (Tencent WeTest, Testin Cloud Test Community, MeterSphere Open Source Community, AITest Localization Community, PerfMa Quality Technology Community, Thoughtworks Community, CSDN Community), and this survey was conducted in 21 communities last year. Based on the title, 5 new questions have been added:

  1. Test team/staffing situation;

  2. Which of the following quality engineering activities has/is currently being carried out by your team?

  3. Software testing automation level, what percentage of functional test cases has been automated?

  4. Which of the following tool combinations is your team currently using to build quality access?

  5. In which quality projects does your company hope to increase more investment in automated testing/tools next year?

Therefore, the survey data is more comprehensive and valuable. Just as a student who participated in this survey said: Participating in the survey is actually a process of reflection in comparison with your own team. Although there are less than 30 questions, it is almost every The soul torture of an investigator runs through the entire life cycle from requirement quality, design quality, code quality, test quality to post-launch quality. A handful of findings had previously been revealed .

The amount of survey data in 2021 has also increased significantly, with a total of 1,356 valid responses received , with an average completion time of 10 minutes and 26 seconds. Some students are also very serious. They wrote a lot in the column "I feel the same about the hard work for a year. What do you want to say about the software quality?" Some of the thoughts are as long as more than 500 words, which moved us very much.

The research and development environment (humanistic environment) of many large factories is relatively good, the leaders are knowledgeable, and the management is humane. However, in reality, there are still many teams working in a bad working environment. After the Spring Festival, they want to escape from such an environment (company). Many students are in pain and often shout out "It's too difficult! I can't do what I want!", "It's important, but it's easy to be ignored, it's too difficult!", "It's relatively numb, and the leader doesn't pay attention! " "It's too hard and too tired", "So tired", "Tired, really tired", nearly 20 students shouted "It's really not easy", "It's not easy", " Software quality is not easy to say that I love youThere are also 7 or 8 students , and some students complained that "the norms are chaotic", "the process is chaotic", "management is chaotic", "it all depends on the crowd", "I am confused and numb"... These all show that Some low-level test engineers, quality managers, and even test managers and quality managers are very painful and helpless, and have to cry out. For this reason, we are here to help them appeal to their leaders and management: they should immediately pay attention to quality, improve their quality management awareness, and adopt effective methods, processes and tools to build high-quality software as soon as possible.

In addition to those heart-piercing shouts, here are some relatively rational voices for everyone to understand some of the dark sides of software quality.

1. The level of personnel is uneven, and the views on quality are inconsistent. The company does not have a good top-down emphasis on quality system, so it is very difficult and tiring to implement quality assessment and tools .

2. I just transferred to work as a quality personnel this year. I have been exposed to more and different projects within the company and encountered various problems in the projects. Overall issues focus on requirements management and R&D specifications. The road to implement process quality improvement has just begun, and it is more tiring to implement process obstacles .

3. In the IT industry, quality is the most difficult thing to do. During the test, it is found that the requirements need to be changed. In order to catch up with the progress of the project, the ducks will be put on the shelves, and there will be a thunderstorm on site. Quality is very important, but many companies say that Emphasis on quality, building this system, strengthening that management, but not giving money when asked for, and then summing up throughout the year: this year's quality work is not in place. Doing a good job in quality will definitely mean an increase in input costs. If money is not approved, power will not be given, so what about quality? Habitual oppression, holding low-level salaries, doing high-level work, good quality work, good team atmosphere, forcefully forced away those who can do the work .

4. R&D process, R&D efficiency, and R&D quality are talked about every day, but they always do things that violate the rules. They want to improve the quality of the release, but the schedule is advanced again and again, and the demand is also very unclear. Complaining to each other and problems continue , The burden of history is heavy, and I can only sigh with emotion to fight again in the coming year .

5. Because it is an internal project, the programmers in charge of development do not pay much attention to user experience, resulting in low user experience and decreasing usage rate. Secondly, the members who are responsible for connecting with customers cannot solve technical problems, the communication is not smooth, and the user experience is not good. Finally, limited funds lead to the inability to expand personnel, which is also an important factor in the inability to improve software quality .

6. Every link from demand quality, development quality, and test quality is a product quality factor, especially the more upstream the link, the greater the impact, so to improve quality, we need to start from the root. A clear system of checks and constraints between product development is extremely important. But often some companies do not have the same department for product development, and there is no mutual restraint system, so customers often complain about system defects, many of which are caused by design. The road to quality is long and difficult , hope it will get better and better!

7. In traditional industries, testing itself plays an important role. It can be said that it is a very important hurdle to ensure quality. With the influence of the concept of testing to the left and de-testing, the requirements for the ability of testers are getting higher and higher, but for The important cognition of testers is getting lower and lower, especially when the traditional industry is subject to the constraints of the institutional framework and the impact of rapid iteration under the Internet microservice architecture, it is growing tenaciously in the cracks .

Of course, there are also a lot of happy sharing, sharing of successful experience, and more than 300 selected golden sentences, all in the "2021 Domestic Software Quality Survey Report", more than 40 pages, hoping to give you some inspiration and help.

If you want to download the full text of the "2021 Domestic Software Quality Survey Report", please follow the official account of "Software Quality Report" and enter "2021 Quality Survey Report" to get it.

 

Guess you like

Origin blog.csdn.net/KerryZhu/article/details/122572904