The bug single complement method of exploratory testing

The bug single complement method of exploratory testing

Exploratory testing through the bug itself.

Accurate bug description, can easily locate the problem.
Vague or misplaced bug descriptions will increase the difficulty of troubleshooting and go on the wrong track.

First, describe a complete bug based on the phenomenon.

Then try to replace the words by word, exact bug in the relevant parameters, environment, definition of the scope of the description, no ambiguity.

Finally, after the exact description of a bug, try to complete the test in some ambiguous, pre-and post-conditions.

IMPORTANT: Each replacement/complement word (condition) is equivalent to an exploratory test!

650) this.width=650, "title=" 2016-05-10_9-57-36.png "style=" Float:none; "alt=" Wkiom1cxqunwiofoaafgvmxqtjg896.png " src= "Http://s1.51cto.com/wyfs02/M00/7F/E5/wKiom1cxQunwIofoAAFGvmxqTjg896.png"/>

650) this.width=650, "title=" 2016-05-10_9-58-01.png "style=" Float:none; "alt=" Wkiom1cxquugsf_gaagkvfw8axm306.png " src= "Http://s5.51cto.com/wyfs02/M01/7F/E5/wKiom1cxQuugSf_gAAGkVfW8aXM306.png"/>

Very strange, can only copy and paste, can not type, so put an outline and pure dry.

This article is from the "Willow" blog, please be sure to keep this source http://eilfei2000.blog.51cto.com/2956473/1771683

The bug single complement method of exploratory testing