[Program life] a tester's reflection!

[Program life] a tester's reflection! -- Linux general technology-Linux programming and kernel information. The following is a detailed description. I am an assistant test engineer who has just been outputted. Hey hey, I am in this position. However, I care about things, but it is not limited to the title itself. As an undergraduate who just graduated from a recent university, I do not have any experience, although I may have done many jobs. In the last two years of college, I started a company, R & D, UI, sales, planning, and even core management. But I don't want to mention this, because many of them don't accept these experiences. After graduating from college, I chose software testing, an industry with many new opportunities. Why did I choose this career? In fact, I may not even know myself. What I think about is simply more attempts, more accumulation, and the status quo seen on different sides. I think it will be an interesting experience. This is my decision. I am willing to try it, even if it takes a lot of time.


As an assistant test engineer with some development experience, my current job is to execute test cases written by my colleagues. However, in actual work, they often jump out of their ideas and rethink the entire test, which of course takes some time. But I think everyone has a narrow logic. We cannot consider all coverage. This is an inevitable topic. Of course, this is also part of growth and exercise. I think any test engineer needs to grow up step by step. But this approach is not necessarily the most effective, because we try to skip the so-called business logic and code logic during the accumulation process, so that we will spend more energy and time testing them. As a tester, this is the most distressing problem. We don't even have time to think about the continuous upgrade and testing of the version. We just need to repeat those steps every day. Over time, you get tired of such a life. What else do you want? From one product to another, we know that N bugs cannot be solved. Because these are developers' tasks, what we can do as a test is to discover bugs.

What I want to talk about is another question that I have been thinking about since entering the company? As a test engineer, how should we think about how to improve our work? Because there is always a bottleneck in everything and I don't want to do anything without a plan. Because those things that do not have a chance will only lead me to delay time and may not even get a result. Compared with development, in the eyes of test engineers, what we focus on is nothing more than engineering improvement. At the same time, what we lack most is the experience in the project, move to a more advanced position than we can control this profession. The role we can play in testing this industry can only go down like this. This is what I didn't want to see. It was also what I didn't want to see during the test. I chose to test the industry for a wider range of ideas and a better way of thinking, but I did not notice many limitations in the industry. If you want to better test your program, you must know how it is implemented. More importantly, you can know what programmers are writing, rather than testing the pure black box. Because each requirement is different, what is the requirement? They are just a constraint and provision. The way everyone understands and defines it is also different. Such a requirement error will lead to product failure and complaints from the end customer. As a tester, we should focus more on development, processes, and quality systems. This is not only for ourselves, but also for the company and for our products. In this way, someone will scold me, and you are not the boss. Why can your boss take millions and we can only take thousands. However, I always think that this is a kind of accumulation and experience. It doesn't matter when you experience it. Naturally, you can see your return at that stage. Because of the benefits you have planned for a long time, output and investment can be regarded as projects, only to see if you can seize the opportunity.

Finally, I am very tired as a new employee. Because I want to balance development and testing, rather than testing itself. A good technology should be tested-driven development, rather than implementing everything. A poor function is handed over to the test. It is a painful experience for testers themselves. For the health of others, please be a good developer. From the perspective of testing, I think about development and who should the CPU serve?