"Purple Ox" is a very hot word recently fried. Concern
InternetFriends have long been familiar with. Popularly speaking, can use three core words to generalize its characteristic: "Difference", "minimalist goal", "go all Out". Today, we would like to discuss this has guided the "millet" rich, "cheetah
Moving"The methodology for listing, how to contribute to the success of QA team building."
"Differentiation"The Ancients Cloud: "With the person to make the final person, playing independently is lifelike". What is differentiation? As the name implies, that is the difference between the things, then first look at several typical counter-examples: 1)crazy overtime, kill envy, there may be a little chance of things. 2)wait for the opponent to make a mistake in order to overtake the bend. 3)most teams (people) are repeating every day and cannot be taken as a "highlight" thing. including but not limited to the above-mentioned cases are not good. Why? Aside from the big circle of the Internet, focus on team management within the company. I believe there is a word that everyone is familiar with--"KPI". You must have asked yourself a question, "How can I Be good?" "or" How do I do better than others? "If the supervisor tells you to try harder than others, that is not to say." This is a law because the Internet does not support idlers. If the supervisor only tells you to "spell
workStrength, spelling and meticulous degree, technical strength ". You have done, the final performance results are not satisfactory, then I can tell you, this is not your fault. Your boss is too mediocre. It is not difficult to think carefully
use case Design, rigorous use case execution, and even necessary overtime to drive the project progress. These are the basic requirements as a QA staff. Even if you do a good job, performance is nothing more than a standard. What reason did your boss say you did "good"? Lost results-oriented, everyone can only work overtime to prove to leader that you are better than others to be more responsible. If you are in this situation, be wary of four words "Wasted Time". Just as mediocre leader always like to let employees do something mediocre, long time to build a mediocre team. I don't think anyone wants to see that. Then the rejection of mediocrity, first of all to achieve differentiation. Do things that are likely to succeed even if your strength is not so strong. The so-called: "A good goal is half the success". Sharing some of the ideas of differentiation is a valuable consideration. Client is responsible for
Functional Testing's classmates. We propose to establish a "quantitative quality system". such as requirements review, use case design, use case execution, communication feedback. These are the jobs that everyone has come to their mouths. Nature is lack of "bright spots". Based on the theory of differentiation, we should do something meaningful and not mediocre. QA is the backbone of quality assurance. People want us to answer a question, "What's the quality of this app?" "And hope that the answer is well-reasoned and objective and impartial." To answer this question is a very meaningful thing. But many teams may not be able to answer this question quickly, or to answer too subjectively. This is also the "quantitative quality system" that I mentioned. The length of the relationship, simply speaking (then there will be a separate
articleThis is a set of scoring mechanisms, with an iterative cycle as a unit, to objectively evaluate the process from project inception to release, including app function testing, adaptation, stability, feedback, and project process monitoring and other aspects of the comprehensive quality. The total is divided into 100 points, each of which is progressively assigned weights. After the system operation, not only can quickly answer the comprehensive quality situation. And can objectively assess the quality of the short board is located. Continuously optimize product quality through continuous exposure issues, traceability issues, and improved scoring. Through a certain amount of time accumulation, but also can master the objective law of app quality. For example, in the requirements review, it can be said that based on quantitative data, the degree of change in demand will affect the quality of the app. Thus play the role of risk control. As for
Performance Testing, differentiation lies in the gradual formation of a field of "standardization." For example, for security or tool-type software. Start speed, garbage scanning speed, garbage cleaning speed, how fast to calculate the standard? Power consumption, how is CPU consumption normal? This, of course, requires constant analysis and accumulation to be persuasive. But more importantly, have you already started? As for the construction of test platform, differentiation lies in learning to think differently. Because you are making a product, how can you make the user like to pay? Nature is outstanding cost-effective! The price/performance ratio of the platform is that it allows users to get the most powerful functions possible (including but not limited to data analysis, visual processing, intelligent control, automatic reporting) through the simplest possible access steps. With this as the starting point, to make a differentiated test platform, or it can only be behind closed doors. Very few people use it.
Application of "turn" "Purple cow" methodology in Test team
