A: How to be a test Manager for a project !!!

Post address:

Http://bbs.testage.net/viewthread.php? Tid = 4588 & pid = 184557 & page = 1 & extra = page % 3D1 # pid184557

Post address:

Http://www.blogjava.net/lijun_li/archive/2008/12/20/247533.html

Case Description:

Briefly describe my problems:

Other departments of the company have a project that requires strict tests. If you request support from our department, the Department will assign me the responsibility. Since the project was just started, the Project Manager said that the testing personnel are not yet determined and I am only one person at the moment, so I have been writing test plans and test cases since I came here, as you have done before. But this morning, my supervisor called me and told me that I was very touched. He said that other departments asked us to support the test, hoping that we could bring them more professional testing ideas and methods, rather than simply asking us to find bugs for the program. I should think more about how to do a good job of testing, think clearly about the entire process, what resources are needed, how to arrange them, and boldly ask the project manager, instead of following the progress of the project, in this way, we cannot reflect the value of our department. I think he makes sense, but to be honest, I am not very clear about what the test Manager of a project needs to consider, pay attention to, and do. I hope you can give me some suggestions. Thank you!

My reply:

This post was posted three years ago. I came back to read this post today. For so long, no one gave me a good idea to talk about how to be a project testing manager, maybe this question is too big. Let's talk about my point of view today.

For the test Manager of a project, the organizational structure and project management mode of each company are different. To do a good job as a test Manager of a project, you must first reach a consensus with the development director and project owner, it is a consensus on the software quality of the project. For the speed, cost, and quality, the three aspects are more biased towards that side, or both.

Of course, from the perspective of testing, we hope that the software quality is very high, so we should stand in the project test, as a test, to understand what can be done? What is the role?

Once the program is submitted to the test, the progress can be controlled by the test party.

I have read the description of the case in this post. The currently annoying problems are:

1. The leader said that other departments asked us to support the test. They wanted us to bring them more professional testing ideas and methods, rather than simply asking us to find bugs for the program.

2. I should think more about how to do a good job of testing, think clearly about the entire process, what resources are needed, how to arrange them, and boldly ask the project manager, instead of following the progress of the project, it does not reflect the value of our department.

From the above description, we can see that the department leaders may say this because:

1. There is no process control point during the project testing process. Specifically, there is no specific work plan (when and how many people do the tests ?)

2. After the program is submitted for testing, there is no definite point when the program can be released or whether it can be released. The project manager does not have his own opinion on the test. The project manager will explain how to proceed with the test progress.

To test the project well, I want to have the following qualities for reference only:

1. Have a deep understanding of the entire testing process, that is, the testing requirements, test plans, test cases, test reports, and bug analysis that need to be done during the project testing work.

2. Collect problems during the testing process, understand the testing progress, and report the problems and progress to the project owner.

3. Good communication and coordination skills, response to demands changes during the testing process, slow bug modification progress, and delayed development submission.

4. Good working pressure and adaptability. As a test leader, the following testing executors will be confused if they cannot withstand the attacks.

5. Find a good solution to the problem

6. Caring for the performance of the team members, empathy, etc.

Think of this for the time being. I hope it will help the upstairs landlords !!! Good luck!