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

I have been busy with my work recently. I haven't posted here for a long time. I'm really sorry! What has kept you so busy lately? Still busy with test architect's work. My work in the past few months has made me have a deeper understanding of test architect. Just tell me what I've done recently. First of all, I went deep into each field to understand how they do testing, the scope, strategies and methods of testing, especially call processing. In order to have a better understanding, I also did some case. I have chatted with technical leader in every field, recorded their current problems, and found ways to help them solve the problems they raised. As a matter of fact, I am very confused because the so-called technical concept of support is very vague. If the experimental equipment is not enough, there are project managers and line managers to solve the problem. If test automation is needed, there is a test automation project team to solve the problem. At first, I spent a lot of time on test automation, but it turned out that the time was wasted, because it was basically the automation project manager who went directly to the technical leader of each group, and my enthusiastic participation caused the dissatisfaction of the person in charge. At the beginning, I wanted to propose careful selection and not to launch blindly. Unfortunately, the pressure of test automation is great, and the personal experience of the project manager has determined the result of the selection, so I can't say anything more. Later, by actually starting to do the test, I found that the current situation was not what the technical leader said, but much worse than that. I just realized that we don't attach great importance to test plan's review,test report's review. Case is written in a variety of ways, including Spring and Autumn semantic, garrulous, and there is basically no check and record of coverage. I began to shift the focus of my work to testing coverage of requirements. Surprisingly, colleagues in some groups did not look at the system requirements documents at all, but directly looked at the implementation documents, and many system requirements were left out. When their test plan review, they care more about the details than about the requirements coverage, scenario coverage and error case of the tests. In fact, these are the focus of the test, not the specific steps. Without a test report, there is no way to know the quality of the software, and there is no feedback from the testers. I began to require that all test plan's review meeting be added, and that there must be a test report's review meeting. Quality Manager and I also developed the template of test plan documents. In fact, these things used to exist and were thrown away after Agile. Of course, we also add a chapter on testers' feedback on software quality. I designed a checklist table to help testers check and record case coverage, and pass the checklist together during plan review. Testers have an interesting mindset. When I propose to add case or add steps, they are usually very disgusted, as if it increases their workload and makes it possible that they will not be able to finish the task. I wrote an article telling everyone that the job of the tester is not to pass case, but to find the bug of the system through the execution of case. It's our job to find bug. We must make sure that when we case pass, our system work is OK, will make users satisfied. Failure to do so would be dereliction of duty. As long as there is something wrong with the system, we can solemnly refuse to let case pass, instead of releasing water with mercy. You know, if you release the water, the responsibility lies with the testers. In order to enhance internal information sharing, we bought a server dedicated to file sharing. We have set up a four-member team to organize and introduce the documents so that all testers can find the information they need as quickly as possible. I have set up an internal technology exchange website to enhance the exchange of information and experience among testers, but unfortunately, only a few people visit it frequently, and most of them almost never visit this site on the pretext that they are busy with their work. I have shared a lot of useful tools and personal experiences on the internal website, but the effect is not obvious. People are still used to receiving information passively by email. I had to write articles and send e-mails at the same time. In order to reduce the number of meetings, I helped to record the whole training process and make it into a video, so that people can flexibly arrange their time for training and listen to the lectures over and over again. I have made a lot of videos, and the results are good so far. I have reduced the frequency of hands-on teaching by some experienced engineers. I also hope that this method can help you increase your ability and habits of self-study. Generally speaking, I am hardly doing any technical work, but I am doing some chores, more like a handyman. The only thing that is technically relevant is to participate in the development of the latest release requirements. Because of the need for early involvement, we testers are required to participate in the requirements development of the new feature and put forward testability-related opinions. Part of my main work is also this, along with the feature owner assigned by our department, to join the requirements development process. This process is still quite interesting, and it is also my favorite. Another job is to sort out the bug of the customer newspaper, analyze what is missing in our work, and make up in time. This work is rather tedious, but it is also meaningful. As Weinberg said, complaints are a sign of quality problems. Sorting and analyzing complaints is a powerful tool to show all testers and managers how bad our work is. Well, busy, write so much first, I hope my efforts will not be in vain, our quality will be improved.

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.