A hodgepodge of test management

Test Management FAQ One.

1. What is the test team structure?

Most test teams, or traditional test teams, typically build team systems by test type, as shown in the figure:

Advantages: The division of functions is clear.

Disadvantages: Single skill development and high coordination cost.

Some of the teams build the system according to the test granularity, as shown in the figure:

Advantages: Test in advance.

Disadvantage: Testing costs are high.

Others follow the test phase or test capability to build the system, which is usually said as the assembly line, as shown in the picture:

Advantages: Fast test speed.

Disadvantage: Test career development is easy to form a bottleneck.

There are a handful of teams that build systems based on test expertise, and this is a much-touted structure now, as shown in the picture:

Advantages: Low test cost.

Disadvantage: Easy to break away from the real business.

The above structure itself has no difference, can combine the actual situation of the team to choose. The structure of the team is currently the first, third and fourth hybrid, as shown in the figure:

Advantages: Maximize resource utilization.

Disadvantages: more parallel work.

2, development needs what kind of test?

Short test time

High test quality

Good at communication

Professional

Deep understanding of products

.....

Casually can list a pile of requirements, but in fact, the core of a, can do development do not do. Wen Tao has a major in the surgery industry, testing its own professional field, the core values of testers should be reflected in where? The relationship between development and testing is both clear-cut and harmonious, and a team leader should be able to identify exactly what role the Test team is in the current development system. This sets the team goal to determine the direction of the team, rather than head to the confusion, or isolate the Test team to set goals alone. Technical Reserve is very important, but the direction of technical reserves depends on the leader to determine, than the development of more understanding test than testing more understand development, this joke said out really very sad, because Sibuxiang.

The general Test team goes through this process:

First, whatever else is needed to satisfy the basic test requirements.

Rise, common functional tests tend to mature, start to introduce performance, automated testing, and so on, the use of third-party testing tools.

Breakthrough, there is considerable testing accumulation, there are more abundant testing resources, began to establish a unique test system, including a variety of methodologies and testing products.

Smooth, should do seems to do almost, also can't think of any revolutionary ideas, to maintain the status quo, began writing biography.

Slipped, bloated, without passion.

The test team that I have seen are mostly in the "breakthrough" stage, at this stage should pay attention to the relationship between technical research and practicality.

Say for a long time, in fact this question should become, what kind of test team the enterprise needs.

3. What kind of test does the boss need?

What's the difference with the above question? Yes, it's a group test requirement, and here's the individual requirements for testing.

First of all, the boss here refers to the entire research and development system in charge of what products, development, testing in his.

Second, for one thing, most bosses don't have much insight into the field of testing, and the perception of testing is more about the feedback from other teams and the final quality of the product. So what is the test question that the boss is most concerned about?

Test costs: How much can I gain from testing? This is a question that every boss will ask. ROI is an account of everyone's heart. The author has always explained that the resource utilization maximization, the energy conservation reason, is proposes uses the least resources to do the most thing, wants one person to undertake many tasks rather than many people to do one thing. Talking about this a lot of people will say you when we don't know the question is how to do it. How to reduce the test ratio the following will be mentioned, but the author first wants to ask, as a supervisor, do you really want to shrink the size of the team? Is it because other factors want to expand?

Technical content: Whether a business is mainly commercial or technology-based, this does not cost the brain to think more, at least we are doing technology. What does the test technology contain? As mentioned above, there is no repetition. If you still don't know, you can refer to the author's series of articles. In this case, it's old-fashioned and simple, and there's a lot more to it than the flaws that others can find, no matter what technique you use in the process. You said you used a lot of sophisticated technology results leng a flaw did not find, useful?

Product quality: This one needless to say, defect prevention is kingly.

Team collaboration: If you think that development and testing are two teams, then there must be two. The division of functions is clear, but it is very problematic to sweep the snow from the front. This fault is developed not related to testing, once there is this idea of how to talk about collaboration?

Admittedly, in the entire research and development system, testing is not the core, at least in today's various research and development processes it is not. With that in mind, it will be clear what kind of Test team the boss needs.

4. How to improve the test development ratio?

Test development ratio should be 1:3?1:4?1:10? even without testing. This is a philosophical question, and the debate is endless. However, I still want to say that simply talking about test development is meaningless, it involves too many factors, is definitely not the higher the better.

A number of practical and effective ideas for raising the proportions:

Conservation of energy: the test workload will not disappear but will only be transferred, transferred to the machine, transferred to the non-testers. At present, most teams are moving to machines, which is why automated testing is enduring. On the digression, although the author does not think that the automated test is silver bullet, but admits it is at least a bullet. Then there is a small part of the team's approach is to transfer to people, that is, the test work out, divergent to the unprofessional tester. Frankly speaking, it is very easy to carry out testing activities, is the individual can come to test. To achieve this, a prerequisite must be met, and the products to be tested are highly measurable. This is the author has been advocating the national test, testing factory, fool and so on and so on. How to improve the product testability, see the author of another article, "Testing means diversity."

Test inheritance: Hundred years old shop, the first inheritance. The benefits of this thing do not want to say more, when your team staff turnover rate is high when you realize. The inheritance must have the system, has the vein, absolutely cannot make the scattered massive information. The specific practice may refer to the National Library, the archives. The author has been doing product test choroid, that is, for a variety of product function points, respectively, the method to be used to test, and the various points to string up to form a similar structure like the human meridians.

Technical innovation: Intelligent testing is not long, the author of the study for many years has no effect, shame. How long has it been that the testing industry has not seen the epoch-making revolutionary innovation? Just say the big and small test tools that look away, which one is different? Science and technology is the first productive force, at the same time, science and technology need to transform into productive forces, as far as possible to avoid developing impractical technology, Not to develop the skills that are not practical and difficult to demonstrate. I suggest that you integrate a variety of testing methods into the business products, but also the product itself has a test function, now many testing tools to achieve the functions can be put in. Finally, look forward to the industry's testing experts, can develop a truly revolutionary, epoch-making test products, is looking forward to.

5. What is a good test supervisor?

The male wants the handsome female to be beautiful, really, does not joke. Did not see in ancient times into the officials of the literati pay attention to handsome, long to be a loser can give you down to tan. So the first element is the image temperament is good, it is better to have a good eloquence.

Second, do not work overtime, do not read wrong, at least not blatant add, to add sneaky. Supervisor long-term overtime in the company is easy to form overtime culture in the team, and even caused the crew to deliberately put some of the work to be completed after work. Once the formation of this atmosphere on the efficiency will cause great damage, we will want to work overtime anyway, not urgent. Busy or busy, everyone in the heart are clear, the most important thing is to get the results, can take care of where you work overtime.

Third, is the technical or management or mixed-type is not bad, but can not be nothing, to have one hand in the whole team can not be compared. Of course, refers to the work of the ability to use, if eating more than others eat that you are at most a good-for-nothing. The digression, the ability and the position does not match very painful, does not have the corresponding ability or does not sit this position good. A person to do things to speak talent, not what ability can be developed.

Finally, accurately evaluate the work and allocate the work reasonably. This is very difficult to do, just find a book in the management of this project at least half of the talk about this. In the case of insufficient resources and a lot of work in parallel to achieve a reasonable distribution that is even more difficult, if this form can also allow the team to operate normally and do not work overtime, come, let everyone call you a master.

In the end, good supervisors are not necessarily good colleagues, they do well in charge and do not need to be exhaustive.

Xiao Kee: From the team structure to the external test requirements, and then to test costs and team managers themselves, in fact, the author of the full text to explain is that in other people's eyes what kind of Test team is a good team, or to get the majority of people approved of the team is what. Many Test team internal problems are not explained, lazy, have time to write it. Opinion, welcome to the brick.