Many testers and test teams are beginning to feel powerless in the increasingly fast-growing iterative projects of the Internet. Many teams and companies are beginning to discuss how to guarantee quality, and the fact is that the quality of the product is not guaranteed by simply starting from the test and testing team. It's time to change from the technical and the intellectual.
There have been a lot of articles on the so-called "whole stack", in fact, at least for now, the real meaning of the "whole stack" has begun to surface over time--the ability to learn quickly and drive the interest of continuous learning.
Whether a team should be so multi-skill, the whole stack of people. In my understanding, a team is in fact not without the whole stack of people, and can not be the entire stack of engineers. But there is a special emphasis on "positioning problems". For example, we found a problem in the normal testing process, we need to be able to determine whether the problem is front-end or back-end, if the backend, then through the various system logs and call relationships need to understand what the problem is on the system. If it's the front end, then we need to find out whether it's a frame layer, a build layer, a business side, and so on. In other words, whether you are functional testing, automated testing or architecture, positioning problems are common requirements.
In fact, the need to test the ability to locate problems, the essence is to improve the efficiency of the entire project process. Because when we find a problem, the previous way is to test to report a bug directly. This bug will describe the context and behavior of the problem. But in fact, development still need to troubleshoot problems, and then fix. That is to say, the process of troubleshooting is unavoidable, and often tests do not know which development of the problem is the head, easy to appear a buck to b,b and then kicked to a situation. So in today's testing industry, most companies simply require testing to have the ability to locate problems, which is also a basic ability.
I particularly emphasize this point, because now the whole industry is pursuing technology. We can see here a lot of sites are cattle hook technology, there are very cattle traversal technology and so on. But the industry has slowly weakened the technical ability to test the original need. such as the development of test strategies, such as the way of testing, test case design, and so on. I am worried that in another 10 years, the test industry is a group of people who are very skilled but don't know how to test. It's like I've heard a lot of tests. Students and I say that many of the company's test directors do not know what the difference is between AB test and grayscale release, thinking that two are a thing. Let me also very worried about the development of the testing industry.
>> stamp, free download function automation Test Tool testwriter~