Test only describe the phenomenon, not to conclude

  We all thought that the test is easy, in fact, the same test with other work, easy to learn but hard to master. You do not say how to find BUG, ​​saying only that describe the problem, most people do not. Sometimes looking for testers to know in person, you would understand what that means. Is this normal? Of course, normal. Describe the problem with writing about the same, even graduated from college, there are a few people can write a good composition?

  In addition to describing is not good, there is a chaotic conclusion mistake. Broadly speaking, there are two scenarios:

  Biased understanding of the problem itself, so conclusions. This encounter more.

  Obviously they are not engaged in technology, we have to put on a master look, to conclude that where there are problems.

 

  As a tester, the most important thing is to accurately describe the problem. This truthfully, easier said than done rarely ah.

Guess you like

Origin blog.csdn.net/quantum7/article/details/93579752