_gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(ga); })();

Guidelines on writing Defect Description

On August 12, 2009 / By admin / In Manual Testing / Reply

Defect can be expressed as “Result followed by the action”. That means, the unexpected behavior occurring when a particular action takes place can be given as defect description.

1. Be specific. State the expected behavior which did not occur - such as after pop-up did not appear and the behavior which occurred instead.

2. Use present tense.

3. Don’t use unnecessary words.

4. Don’t add exclamation points. End sentences with a period.

5. DON’T USE ALL CAPS. Format words in upper and lower case (mixed case).

6. Mention steps to reproduce the defect compulsorily.

Related posts:

  1. Guidelines on deciding the Severity of Defect Indicate the impact each defect has on testing efforts or...
  2. Defect What is Defect?   If software misses some feature...
  3. Defect What is Defect?   Nonconformance to requirements or functional...
  4. Good code What is ‘good code’?   ‘Good code’ is code...
  5. Get result for every action If batch testing is used then the result shown...

Related posts brought to you by Yet Another Related Posts Plugin.

Reply

Spam Protection by WP-SpamFree