Self-cultivation of software testing (i): Repair the Heart three questions _ Test experience

"To teach a person to fish, to teach it to the fishing" is to impart knowledge to people, rather than impart knowledge to the way of learning. Today I would like to focus on this from the thinking level to do another sublimation: "To teach the fish, then the first enlightenment."
Good software testing, the first to have the accomplishment is to understand three problems. This is the "enlightenment" mentioned above. If the developer modifies the bug, we use the idea of "three questions" to test, which will help the testers understand the requirements.
How to realize the "three questions". You will certainly ask: "which three questions." "
For example, let's design a scene: Imagine, you walk on the road, a stranger without further ado slap you in the face.
What do you think of when you are thinking rationally? "I offended him by accident." "," This person is not mentally problematic. "," he mistook the person. Wait No matter what you think, it boils down to a problem, which is "what is the reason for hitting me".
First question: "What is the reason?"
The developer commits a bug that is fixed, and the first question that testers need to understand before they start a test is "what is the cause of this flaw". To facilitate test analysis, test planning, and testing for the cause of the problem. The relationship between things is diverse, in the thinking of software testing into the "first follow-up", "Cause and be caused by" relations, coupled with the materialist dialectics methodology. Can give us a more thorough understanding of the reasons for this flaw, thus further understanding the requirements of the business level.
Through communication, analysis to understand: Walk in the street was slapped because it is too ugly. Some people will have the question: "Although is too ugly, can not slap it." Why the Slap? And that's the second question we have to figure out, "Why do we do this?"
Question two: The root cause-"Why do you fix this?"
Defects can be repaired in a number of scenarios, based on business, technology implementation, design risk, and so on to consider whether the developers have chosen the best solution. Understanding "Why to fix this" helps us to design test cases and comprehensively measure the risk of the test, making it easier to expose the problem and increase the focus on the test points with a greater risk factor.
Aristotle said that all existence is made up of the origin, and that all existence is originally produced from it, and finally reverts to it. Figuring out why to do this will enable us to trace the source of the software testing work to the fullest and develop a test plan. Exposing the defect to a greater degree.
Figure out "The reason for the slap is ugly and hopeless." But then again, you can use language to affect me, why hit me, why do not use language to affect me, why not to hit others.
From the point of view of software testing, the third question we need to understand is "why not?"
Question three: Inspiration--"Why not do that"
As a professional software tester, it is not enough to understand only the cause of the problem and why it is so fixed. From the perspective of divergent thinking, we need to further consider the "another way". This is important. Why do you use plan A to fix this defect, and why not plan B? There is no plan C other than Plan B. Understanding these issues makes it easier for us to become familiar with the business, understand the system, improve test skills, and design test cases. The demand behind these needs is a bottleneck for the growth of many software testers.
I am not, hope that "three questions" as a software testing methodology can make everyone to repair the heart of testing, awareness of the nature of testing. Work out more communication, grow and progress together.
......


To view more highlights of this issue, please click here to download: http://www.51testing.com/html/98/n-1298298.html