how to write good description?

marina marina's picture
marina marina asked on January 18, 2015 - 2:34pm | Replies (4).

how to write good description for bug?

4 Answers

Sujit Kumar's picture

A good bug description format may contain following data:

1. Bug Title;

2. Bug summary: 

3. Steps to reporduce

4. Environment: Win 7, Mozilla, Chrome, IE version

5. Actual Result

6. Expected Result:

6. Severity - Low, Medium, High, Blocker

7. Screen Shot of bug

Krishna b's picture
Krishna b replied on February 6, 2015 - 6:15am.

In addtion to what Sujit Kumar said, add screen shots wherever applicable. Keep discription in bullet points. 

Arifa Batool's picture

For some bugs you can also add 'Observation' a brief summary of what unusal behavior your observed in the application or in a certain feature.

If you have logs available either via 3rd party logging tools (like crashlytics etc) or native logs also attached those (specially in case of crashes) with the bugs.

md jasimuddin shaikh's picture

summary:

precondition:

order details:

steps to reproduce:

expected result:

actual result:

screenshot :

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.