Time: 12:05 PM on Sunday, June 7, 2015
Background: Company B has 20-30 r&d personnel and several new members of the test team.
Question:
1. In the final delivery, the quality of APP products has been poor, with most problems in use;
2. The developer does not participate in the test-related work during the r&d process, and does not know how to ensure the quality;
3, need to set up a professional testing team to be responsible for product quality.
Communication analysis points:
1, process is important, but not the most critical thing, it can help you solidify links, but not help you do things faster, better, the key is the team;
No matter how good the current process is, it cannot help solve the problem. The foundation, accumulation and precipitation of the team determine how far to go.
If you have a process, at this stage is more appropriate to try the whole software testing practices http://www.infoq.com/cn/articles…
2. What the team lacks most at present is not testers, but how much the team (r&d, product, etc.) pays attention to quality;
Whether there are people who care, whether there are deep users, whether there is a connection with the survival of the product, these are all questions to consider
3, the development progress is not fast enough, the quality of development is not good enough, will the pace too big easy to pull eggs;
There will always be technology debt; it’s just a matter of whether it can be paid off or not
The improvement strategy is suggested as follows
1. Find bug reward systems
All staff involved in finding bugs, including r&d, testing, product and marketing personnel, mobilized all available forces to intercept problems to users as early as possible; Eat their own dog food, find bugs to develop scoring mechanism, give rewards.
2. The ease of use of the front-end framework (such as Android) will reduce the development and maintenance costs, and respond to problems more quickly
Reliability and user experience, always have to find a balance, reliability can not be guaranteed, no matter how beautiful the final fact is bullshit,
In the long run, we need to consider the efficiency of front-end interface development, accumulate a group of talents, and ultimately, people to complete.
3. Analyze test points from the stage of product design and requirement
What does that mean? In simple terms, the product is designed as a prototype, all the elements are there, the functionality is determined,
At this point, you can test the prototype diagram without running any app. Of course, if you have someone who knows the business well to analyze it,
Specific methods can refer to the agile mind maps use case practice road: http://www.infoq.com/cn/articles…
The team was able to write out the core test points from the prototypes, and the development process did the rest.
Continuous integration + code analysis
Sonar: Jenkins + Sonar: Support continuous build of Android and Java back end platforms, code analysis, quality loop activities of the daily development process: problem finding -> problem solving -> continue to run code analysis.
5. Analyze the cause of bugs in each version
Why is that? Bugs are valuable lessons, for example:
First, analyze the problem, then analyze the framework that caused the problem, the control, and finally: the technical reasons of their own team, or the official framework problem
I guess a lot of Android developers are not familiar with the features of controls, but they just know how to use them, but they don’t know how to use them better. If this is the case, he can get business done.
However, the reliability and stability of the business process cannot be guaranteed, so the team has a backbone from which problems can be summarized to improve;
6. What is the premise that the team does not need dedicated testers?
All the team members were tested, and all of them were familiar with the business and design. All the business and design had been reviewed and recognized by all of them, and they could point out the key points (that is, the points needing attention in the test).
And there is also a set of effective mechanism to verify the problems of these points, so that the team can completely separate from the full-time testers, so that everyone can participate in the external publicity of Google test and test r & D ratio is 1:10, in fact, a lot of things in the middle, we do not understand, just to look at the surface, Google’s test is more segmentation, There are three roles as shown below;
In addition, test maturity is used to distinguish teams, so do not blindly follow the wind, domestic teams are still not up to this level.
One last point: you have to develop schedule, you have to test quality, and you have to make sure users pay for it.
Strengthen team have both development and testing skills to promote have the ability to break through and lead the team to develop new world, in addition to cultivate skilled professionals, list the key business point test, accumulated experience in related defects library instruction to avoid repeat problem, and now the heaviest if team maturity in ascension, lay a solid foundation, the quality of debt on the most deadly place first.
It’s great to have a picture of the best way to work with mature teams right now, just getting the development phase right.
There was no mention of automation, since the test team didn’t even have a foundation to start with
(wechat official account: Bulletin board of Le Shao)