Software testing awareness of the active thinking _ software Testing

How to think actively in software testing. How to realize the freedom of software testers. How do you understand it?

When the project manager assigns you a job, does he often pay attention to your progress and quality, and if so, you should reflect on it. Let me talk about my understanding of the initiative of Software testers (not including test patterns, etc.)

In fact, first of all to understand the nature of software testing or target, generally can be understood as "rapid release of High-quality products", 2 dimensions, 1 quality; 2 efficiency. No matter what your role is in the Test team, the ultimate goal is certainly so.

I just graduated into the test industry for 1 years, is a software test soldier, from the beginning of the internship and apply to the company to do test execution, now do test design and implementation, 1 years, not long, is still a test soldier, also not short, I think growth can also. As the testing team is still doing test execution (our senior designer will not do test execution), I'll talk about the idea of active thinking in the role of a test executive.

Testers and PM goals are all for the rapid release of high-quality versions, but testers are often responsible for only 1-2 modules, and PM is responsible for the overall progress and quality of the project, then how can we assist PM to do a good job in the role. To get a responsible module, how do we make sure it's tested for quality and progress? I prefer the end-to-end way of thinking, where you can decompose from different dimensions, such as what the module is going to produce, and who audits the module process (our company is PM,PMO).

1, testing Strategy (plan), we have to assist the project manager to develop a good module of the test plan, because in general, the module responsible than PM more understanding of module details, risk points, of course, not less and PM communication. The test strategy is to guide the entire test cycle, and if there is a problem with the test strategy, it will be painful to pay for it later.

2, quality, how to ensure that the module quality has been achieved, the different companies have different means of quality analysis. Get a test module, at the beginning of the test, I first based on their understanding of the module, combined with the previous version of the same module bug, online problem bugs, put forward their own risk points, and then set up the development of the owner, the development of module experts and test module experts to jointly analyze the risk point is Testing process of periodic analysis of the quality of the module, if the quality of the risk to be eliminated in time, such as the module test completed, suddenly there are some bugs, then we have to analyze these bugs are not tested before, or the development of changes triggered, retrospective analysis to do a follow-up improvement measures. Test later, because our company has a PMO (to assist PM management project), they will have a corresponding project defect prevention Library, every time the analysis is completed, I will combine PM Project view, to analyze the previous module which did not do in place, and then to supplement the analysis and then strengthen the test.

3, progress, in fact, good quality is to ensure progress, because if you do not good quality, progress is meaningless, after all, you still have to pay for the quality. Of course, we also have to ensure high efficiency, how to ensure high efficiency here does not do fine instructions, depending on the company's Test module, test platform, and project management and self time management, planning control and other factors. My principle is that the responsible module should never be left behind because of any factors.

4, before I think doing well above 3 points already very good (active discovery solves the problem, avoids the PM always does not trust oneself to be responsible for the matter, regardless of how to let PM rest assured), later saw an article http://www.51testing.com/html/22/ N-817822.html feel that they have to improve, such as summing up their own working methods in the project to share the exchange.

About the tester's initiative to think about consciousness, did you do it. Perhaps, you have a better welcome to share the Exchange ~ ~

This article is reproduced from the 51Testing Software test network, see more: http://www.51testing.com/html/news.html