Test Management hodgedge

Test Management FAQ 1.

1,What is the structure of the test team?

Most testing teams, or traditional testing teams, generally build a team system based on the testing type ,:

 

Advantage: The function is clearly divided.

Disadvantages: Skill Development is simple, and coordination costs are high.

 

Some teams build the system according to the test granularity ,:

 

Advantage: Test advance.

Disadvantage: high testing costs.

 

Another way is to build a system based on the test phase or test capability, that is, the pipeline, which is usually referred to ,:

 

Advantage: fast testing speed.

Disadvantages: Testing career development is prone to bottlenecks.

 

A very small number of teams have built a system based on the test specialization level. This is also the structure that is currently widely promoted ,:

 

Advantage: low test cost.

Disadvantage: it is easy to break away from the actual business.

 

The above structures are not highly competitive and can be selected based on the actual situation of the team. The structure of my team is currently a mixture of the first, third and fourth types ,:

 

Advantage: maximize resource utilization.

Disadvantage: A lot of parallel work.

 

2,What test is required for development?

• Short test time
• High test quality
• Good at communication
• Professional
• Deep understanding of Products
• ......

You can easily list a bunch of requirements, but the core is actually one that can't be done by development. Wentao has specialized skills in its own field. What are the core values of testers? The relationship between development and testing is both distinct and harmonious. As a team leader, we should be able to accurately identify the position of the testing team in the current R & D system. In this way, set team goals to determine the development direction of the team, instead of making a decision, or isolate the test team to set a separate goal. The technical reserve is very important, but the direction of the technical reserve is determined by the leader. It is really sad to say this joke because it is nothing like testing and development.

Generally, the test team goes through this process:

• Caochuang, no matter what other requirements can meet the basic test requirements.
• General functional testing tends to mature, and performance and automated testing are introduced. Third-party testing tools are usually used.
• Breakthrough, a considerable amount of testing experience, a wealth of testing resources, began to establish a unique testing system, including a variety of methodologies and testing products.
• It seems that everything should be done almost, and there is no revolutionary idea. Keep the status quo and start writing books.
• Decline, float, no passion.

Most of the test teams I have seen are in the breakthrough stage. In this stage, pay attention to the relationship between technical research and practicality.

After talking about it for half a day, this problem should actually become the testing team required by the Company.

 

3,What kind of tests does the boss need?

What is the difference with the above question? Yes, the above is the group's requirements for testing. Here is the individual's requirements for testing.

First, the boss here refers to the person in charge of the entire R & D system, where all products, development, and testing are located.

Secondly, I would like to put it bluntly. Most bosses do not have much in-depth understanding of the testing field, and their cognition of the testing is more from feedback from other teams and the final quality of the product. So what is the most important test question for the boss?

• Test cost: How much benefit can the test bring to me? This is a question that every boss will ask. ROI is a ledger for everyone. The author has been explaining the reasons for the maximum resource utilization and conservation of energy. It is recommended that you use the least resources to do the most things. You need one person to undertake multiple tasks rather than one person to do one thing. When talking about this, many people will say that we don't know how to solve the problem. How to Reduce the testing ratio is discussed below, but I would like to ask first, as a supervisor, do you really want to narrow down the team size? Is it because of other factors that want to expand the scale?
• Technical content: whether an enterprise is mainly engaged in business or technology, this does not have to worry about it, at least we are doing technology. What exactly does the testing technology contain? As mentioned above, we will not repeat it here. If you still do not know, you can refer to the author's SeriesArticle. Here, we can say that we are very old and simple. We can find more and more in-depth defects that others cannot find, so we have technical knowledge, no matter what technology or method you use in the process. How many advanced technical results have you used? Failed is a defect. Is it useful?
• Product Quality: Needless to say, Defect Prevention is king.
• Team collaboration: If you think that development and testing are two teams, they must be two. It is okay to clearly define the function division, but it is very difficult to clean the snow in front of the door. This fault is not related to testing. If you have such an idea, what about collaboration?

It is undeniable that in the entire R & D system, testing is not the core, at least in all kinds of R & D processes today. By clarifying this, you can determine what testing teams the boss needs.

 

4,How to Improve the test and development ratio?

Test Development ratio should be? ? ? It is not even tested. This is a philosophical question and there is no end to debate. However, I still want to say that simply talking about Test Development is meaningless. It involves too many factors, and it is definitely not the higher the better.

Here are some effective ideas for Increasing the proportion:

• Conservation of energy: The test workload will not disappear but will only be transferred to machines and non-testers. At present, most teams are moving to machines, which is why automated testing is always booming. Aside, although I do not consider automated testing as a silver bullet, I admit that it is at least a bullet. Then, a small number of teams are transferred to people, that is, to spread the testing work to non-professional testers. To put it bluntly, it is very easy to carry out testing activities, and individuals can come to the test. To achieve this, a prerequisite must be met. The product to be tested has a high testability level. This is also the author has been advocating the national testing, testing factory, silly, and so on. For more information about how to improve product testability, see the author's article "diverse testing methods".
• Test inheritance: a century-old store, with its first re-inheritance. I don't want to say much about the benefits of this stuff. When your team's turnover rate is high, you will realize it. There must be a system and context for inheritance, and there must be no scattered massive information. For details, refer to the National Library and archives. I have been working on the product test context diagram, that is, the methods and methods used to test various functional points of a product, and concatenate various points, form a structure similar to human meridians.
• Technological Innovation: Smart testing is nowhere in the sky, and I have never studied it for many years. How long has the testing industry not seen epoch and revolutionary innovation? Which of the following is a distinctive test tool? Science and technology are the primary productive forces. At the same time, science and technology need to be converted into productive forces, so as to avoid developing impractical technologies as much as possible, and not to show their own capabilities by developing impractical and difficult technologies. The author suggests that you integrate various testing methods into your business products, and that the product itself has the test function. Now, many testing tools can implement the functions. Finally, we look forward to the development of revolutionary and epoch-making testing products by industry testing experts.

 

5,How is a good test supervisor?

Handsome male, handsome female, beautiful, true, no joke. Didn't you look into the ancient times as an official taxi to pay attention to a table of talents, and you will be able to get down to exploring flowers. Therefore, the first element is the excellent image quality. It is better to have a good eloquence.

Second, do not work overtime. If you are not mistaken, at least do not blindly add it. If the supervisor is working overtime in the company for a long time, it is easy to form an overtime culture in the team, and even the team members deliberately leave some work after work. Once this atmosphere is formed, it will cause great damage to the work efficiency, and everyone will want to work overtime. Everyone knows whether you are busy or idle. The most important thing is to take the result and take care of where you work overtime.

Third, there is no difference between technology, management, or hybrid, but nothing can be done. There must be one aspect that is incomparable to the entire team. Of course, it refers to the ability that can be used at work. If you eat more than others, you are at most a bucket. Aside from the question, it is very painful to have the ability to be different from the position. If you do not have the corresponding ability, do not sit in this position. Being a human is a matter of talent, not all of which can be developed.

Fourth, accurately assess the work and rationally distribute the work. This is very difficult to achieve. At least half of the project management books are talking about this. It is difficult to allocate resources reasonably when resources are insufficient and most of the jobs are in parallel. If this mode allows the team to run normally without working overtime, let everyone call you a master.

Finally, a good supervisor is not necessarily a good colleague. Just be a good supervisor and you don't have to ask yourself to be all-inclusive.

 

 

Note: From the Perspective of team structure to external requirements for testing, to the testing cost and the team manager itself, I would like to explain in the full text what kind of testing team is a good team in the eyes of others, or what kind of team can be recognized by most people. Many internal problems of the test team are not described. Be lazy and try again later. You are welcome to shoot bricks.