How to Write a Good Bug Report? Tips and Tricks

Why good Bug report?

If your bug report is effective, then its chances to get fixed are higher. So fixing a bug depends upon how effectively you report it. Reporting a bug is nothing but a skill and I will explain how to achieve this skill.

“The point of writing problem report(bug report) is to get bugs fixed” – By Cem Kaner. If a tester is not reporting a bug correctly, the programmer will most likely reject this bug stating it as irreproducible. 

This can hurt the testers moral and sometimes the ego too. (I suggest not to keep any type of ego. Ego’s like “I have reported the bug correctly”, “I can reproduce it”, “Why he/she has rejected the bug?”, “It’s not my fault” etc.,).

good bug report

What are the Qualities of a Good Software Bug Report?

Anyone can write a bug report. But not everyone can write an effective bug report.

You should be able to distinguish between an average bug report and a good bug report. How to distinguish between a good and bad bug report? It’s very simple, apply the following characteristics and techniques to report a bug.

Characteristics and Techniques include:

#1) Having a clearly specified Bug Number:

Always assign a unique number to each bug report. This, in turn, will help you to identify the bug record. If you are using any automated bug-reporting tool then this unique number will be generated automatically each time while you report the bug.

Note the number and a brief description of each bug that you reported.

#2) Reproducible:

If your bug is not reproducible, then it will never get fixed.

You should clearly mention the steps to reproduce the bug. Do not assume or skip any reproducing step. A bug which is described Step by step is easy to reproduce and fix.

#3) Be Specific:

Do not write an essay about the problem.

Be Specific and to the point. Try to summarize the problem in minimum words yet in an effective way. Do not combine multiple problems even if they seem to be similar. Write different reports for each problem.

Effective Bug Reporting

Bug reporting is an important aspect of software testing. An effective bug report communicates well with the development team and avoids confusion or miscommunication.

A good bug report should be clear and concise without any missing key points. Any lack of clarity leads to misunderstanding and slows down the development process as well.  Defect writing and reporting is one of the most important but neglected areas in the testing life cycle.

Good writing is very important for filing a bug. The most important point that a tester should keep in mind is not to use a commanding tone in the report. This breaks the morale and creates an unhealthy work relationship. Use a suggestive tone.

Don’t assume that the developer has done a mistake and hence you can use harsh words. Before reporting, it is equally important to check if the same bug has been reported or not.

A duplicate bug is a burden in the testing cycle. Check the whole list of known bugs. At times, the developers might have known the issue and ignored for a future release. Tools like Bugzilla which automatically searches for duplicate bugs can also be used. However, it is best to manually search for any duplicate bug.

The import information that a bug report must communicate is “How?” and “Where?” The report should clearly answer how the test was performed and where the defect occurred exactly. The reader should easily reproduce the bug and find where the bug is.

Keep in mind that the objective of writing the bug report is to enable the developer to visualize the problem. He/She should clearly understand the defect from the bug report. Remember to give all the relevant information that the developer is seeking.

Also, bear in mind that a bug report would be preserved for future use and should be well written with the required information. Use meaningful sentences and simple words to describe your bugs. Don’t use confusing statements that wastes the time of the reviewer.

Report each bug as a separate issue. In case of multiple issues in a single bug report, you can’t close it unless all the issues are resolved.

Hence it is best to split the issues into separate bugs. This ensures that each bug can be handled separately. A well-written bug report helps a developer to reproduce the bug at their terminal. This helps them to diagnose the issue as well.

How to Report a Bug?

Use the following simple Bug report template:

This is a simple bug report format. It may vary depending upon the bug report tool that you are using. If you are writing a bug report manually then some fields need to be mentioned specifically like the Bug number, which should be assigned manually.

Reporter: Your name and email address.

Product: In which product you found this bug.

Version: The product version if any.

Component: These are the major sub-modules of the product.

Platform: Mention the hardware platform where you found this bug. The various platforms like ‘PC’, ‘MAC’, ‘HP’, ‘Sun’ etc.

Operating system: Mention all the operating systems where you found the bug. Operating systems like Windows, Linux, Unix, SunOS, Mac OS. Mention the different OS versions also like Windows NT, Windows 2000, Windows XP etc, if applicable.

Priority: When should a bug be fixed? Priority is generally set from P1 to P5. P1 as “fix the bug with the highest priority” and P5 as ” Fix when time permits”.

This describes the impact of the bug.
Types of Severity:

  • Blocker: No further testing work can be done.
  • Critical: Application crash, Loss of data.
  • Major: Major loss of function.
  • Minor: Minor loss of function.
  • Trivial: Some UI enhancements.
  • Enhancement: Request for a new feature or some enhancement in the existing one.


When you are logging the bug into any bug tracking system then by default the bug status will be ‘New’.
Later on, the bug goes through various stages like Fixed, Verified, Reopen, Won’t Fix etc.

=> Click here

to read more about detailed bug life cycle.

Assign To:

If you know which developer is responsible for that particular module in which the bug occurred, then you can specify the email address of that developer. Else keep it blank as this will assign the bug to the module owner if not the Manager will assign the bug to the developer. Possibly add the manager’s email address in the CC list.


The page URL on which the bug occurred.


A brief summary of the bug mostly in 60 words or below. Make sure your summary is reflecting what the problem is and where it is.


A detailed description of the bug.

Use the following fields for the description field:

  • Reproduce steps: Clearly, mention the steps to reproduce the bug.
  • Expected result: How the application should behave on the above-mentioned steps.
  • Actual result: What is the actual result of running the above steps i.e. the bug behavior.

These are the important steps in the bug report. You can also add the “Report type” as one more field which will describe the bug type.

The report types include:

1) Coding error
2) Design error
3) New Suggestion
4) Documentation issue
5) Hardware problem

Important Features in your Bug Report

Given below are the important features in the bug report:

#1) Bug Number/id:

A bug number or an identification number (like swb001) makes bug reporting and referring to a bug much easier. The developer can easily check if a particular bug has been fixed or not. It makes the whole testing and retesting process smoother and easier.

#2) Bug Title:

A bug title is read more often than any other part of the bug report. It should say all about what comes in the bug.

The bug title should be suggestive enough that the reader can understand it. A clear bug title makes it easy to understand and the reader can know if the bug has been reported earlier or has been fixed.

#3) Priority:

Based on the severity of the bug, a priority can be set for it. A bug can be a Blocker, Critical, Major, Minor, Trivial, or a suggestion. A bug priority from P1 to P5 can be given so that the important ones are viewed first.

#4) Platform/Environment:

The OS and browser configuration is necessary for a clear bug report. It is the best way to communicate on how the bug can be reproduced.

Without the exact platform or environment, the application may behave differently and the bug at the tester’s end may not replicate on the developer’s end. So it is best to mention clearly the environment in which the bug was detected.

#5) Description:

Bug description helps the developer to understand the bug. It describes the problem encountered. Poor description will create confusion and waste the time of the developers and the testers as well.

It is necessary to communicate clearly about the effect in the description. It’s always helpful to use complete sentences. It is a good practice to describe each problem separately instead of crumbling them altogether. Don’t use terms like “I think” or “I believe”.

#6) Steps to Reproduce:

A good bug report should clearly mention the steps to reproduce. The steps should include actions that cause the bug. Don’t make generic statements. Be specific in the steps to follow.

A good example of a well-written procedure is given below-:


  • Select product Abc01.
  • Click on Add to cart.
  • Click remove to remove the product from the cart.

#7) Expected and Actual Result:

A bug description is incomplete without the Expected and Actual results. It is necessary to outline what is the outcome of the test and what the user should expect. The reader should know what the correct outcome of the test is. Clearly, mention what happened during the test and what was the outcome.

#8) Screenshot:

A picture is worth a thousand words. Take a Screenshot of the instance of failure with proper captioning to highlight the defect. Highlight unexpected error messages with light red color. This draws the attention to the required area.

Some Bonus Tips to write a Good Bug Report

Given below are some more additional tips to write a good bug report:

1) Report the problem immediately:

 If you find any bug while testing, then need not wait to write a detail bug report later. Instead write the bug report immediately. This will ensure a good and reproducible bug report. If you decide to write the bug report later on then there are high chances to miss the important steps in your report.

2) Reproduce the bug three times before writing a bug report: 

Your bug should be reproducible. Make sure that your steps are robust enough to reproduce the bug without any ambiguity. If your bug is not reproducible every time you can still file a bug mentioning the periodic nature of the bug.

3) Test the same bug occurrence on other similar modules: 

Sometimes the developer uses the same code for different similar modules. So there are higher chances for the bug in one module to occur in other similar modules as well. You can even try to find the more severe version of the bug you found.

4) Write a good bug summary:

Bug summary will help the developers to quickly analyze the bug nature. A poor quality report will unnecessarily increase the development and testing time. Communicate well with your bug report summary. Keep in mind that the bug summary is used as a reference to search the bug in bug inventory.

5) Read bug report before hitting the Submit button:

Read all the sentences, wordings and steps that are used in the bug report. See if any sentence is creating ambiguity that can lead to misinterpretation. Misleading words or sentences should be avoided in order to have a clear bug report.

6) Do not use Abusive language:

It’s nice that you did a good work and found a bug but do not use this credit for criticizing the developer or to attack any individual.


No doubt that your bug report should be a high-quality document.

Focus on writing good bug reports and spend some time on this task because this is the main communication point between the tester, developer and the manager. Managers should create an awareness to their team that writing a good bug report is the primary responsibility of any tester.

Your effort towards writing a good bug report will not only save the resources of the company but also create a good relationship between you and the developers.

For better productivity write a better bug report.

Are you an expert in writing a bug report? Feel free to share your thoughts in the comments section below.


#1 srianand

HI, this article is very useful one.It helps me understand effective bug report.

#2 Thulasi Suresh

Really nice to read this article. I personally feel if you could interrelate this with testcase and execution report that it would give more info. Ie. Whatever we log as status fail in the test excution is record as bug.What I mean is what we record in the actual is now turned as issue and the test codition is the steps to reproduce the same.

#3 Sameer S. Mandve

Nice One…………

#4 Mani

thanx for your valuable information. I’m doing my testing course. So if u know any oppurtunities please inform me.

#5 Poonam

Its really helpful!!

#6 Vijay

@Thulasi – It could have created some complications by relating it with test cases and execution. I wanted to focus mainly on effective bug report.

Thanks all for the kind words.

#7 resna

awesome report…i got a job as a TESTER bt i’ve no idea how the bug report looks like?could u pls give an original report? pls help me…i’m goin to join on comin monday…

#8 Gimmy

very Informative

#9 sdpanong

I find this article very helpful and will consider it as a guideline for my report as a Tester.


#10 prabhunair

hi, really it’s a great article.. i’m doing my software testing course right now.. this may help me a lot and i got an overview about bug report..

#11 softwareQA

Thank you so much for your great posts. I read your articles before my interview for a QA position with one of the top software companies in the Silicon Valley. I got the job thanks to your excellent articles!

#12 Vijay

@ resna – I have mailed you the bug report format. One simple report can also be viewed in comment section of post

@ softwareQA – Its great to hear such news. Congrats for your dream job. I am glad that my articles are practically helping to readers.

#13 Chandra Shekar


This article is usefule to every SQA. as my point of view i am new to this, after reading this meself confidence level incresed, thanx

#14 Rajesh

Hi Vijay
Its very good
Can u mail me the bug report ?


#15 varalakshmi prasanna

thanks. the information is very useful do u have information on how to write test cases with examples .as i feel difficult for writing test cases please inform me about testing oppurtunities to my emailid

#16 Yasoda

Thanks you all who are maintainnig this site by providing valuable informations to us with better sequence.

Thank you

#17 kavitha

the article is great,and is very informative for the begineers.

#18 Karthik

I find this article very helpful and will consider it as a guideline for my report as a Tester.

#19 vishala

Hi, this is vishala i got a job as a software test eng. and would like to know about the differenct between the Agile Model and Waterfall Model

I read Bug Report Article it is very good. I hope u can give me answer to any question.
Thank U.

#20 mohini k

hi this is mohini , which is the best model in SDLC to follow for the small projects.

In Waterfall model and Spiral models
thak u

#21 Suresh

Totally I Agree
Useful site for Every one so very nice…….

Suresh B

#22 zakir


Firstly, Small projects need not follow any Models friend and the best among the listed two is Spiral model

#23 Pravin

HI, this article is very useful one.Only terms used while reporting can be changed depend on Bug tracking tool used.

#24 savithri

this is so nice to read. can u mail me bug report

#25 savithri

can u mail me details on energy domain and what are the elements i need to cover

#26 Gatari Mishra

Hi Vijay,

This is Gayatri . I am having 2 yrs exp as a corporate trainer in testing. Currently joined as a test eng. I ahve to work in QTP and QC..

Please Can you give me Testing Process Flow , What we have to do in real time step by step…



#27 Kiran

Really a very good site for testers at all levels.
You can provide some information on free tools.

#28 rajjonnada


Vijay, the tips for good bug report is really cool……
I would like to know if you have any domain i.e., Banking/corebanking/lending relating with testing by telling business flow for Retail Assets/corporate assets/retail liability ?

#29 rajjonnada


If you are working in client place then as per the latest trend all follows V-model where developers, business users and Testers will work together. Which will lead to be productive with best results with time saving and better sharring of thoughts and knowledge with all. There will be very less of misscommunication. Other then that you sprial model is the best one, If you are not working in client side.

#30 rajjonnada

@ vijay

can you mail me personally to the
thank you

#31 rajjonnada


can u give the mail id, i do have some stuff regarding agile and waterfall model if you needed.

#32 raja

This article is fantastic vijay…

#33 raja


Principles of Test Automation
In considering how to approach a systematic and productive test automation effort, it may help to keep the following principles in mind. They are culled from the experience of many test automation engineers and managers, over the last 15 years. Some of them I have explained in detail in my article Test Automation Snake Oil, and in my book Lessons Learned in Software Testing.
Transitioning to Agile Test Automation
1) Establish and announce the role of the test automation team to developers and testers.
2) Establish a reporting system and a dispatching system for the automation team.
3) Make an inventory of known testware within the company.
4) Make a quick survey of testware available outside the company.
5) Have toolsmiths sit with testers, understand how they test, and identify test automation opportunities
6) Create the experience for the testers of making a request and seeing it rapidly granted.
7) Review the progress of the automation effort no less frequently than every two weeks.
8 ) Continue to improve the training of the testers, so that they are better able to conceive of sophisticated test strategies.

see more guide on agile automation here

#34 raja

This is by Mr. James Bach.

#35 suganya

Its reall nice,i can understand how to write a effective bug Report,but please can u send me Original Bug Report Template with some examples.. i am working as a Manual tester.. so please Help me

#36 suganya

u mail me in

#37 Gaurav Garg

It is really good.Through this i understand how to write effective bug report.What are the steps we should follow to reproduce a bug.

#38 Devendra sonpure

i am devendra working as a software test engineer. your report is really good and i am impress to see it

#39 salman

hi all
is Software engineer term can be used for qa

#40 salman

i am new to qa, can any body tell me detail of reproduce

#41 Pravin

please mail me any bug report for sql based next month i will be working on same,please.

#42 kathyayani

please can you mail me the bug report

#43 kathyayani

please can you mail me the bug report

#44 selvam

Vijay you are doing simply the worthful job.really great

#45 selvam

Please can anyone send me the original bug report..

#46 vijay

>>hi this is mohini , which is the best model in SDLC to follow for the small projects.

In Waterfall model and Spiral models

@mohini k

r u working? how many SDLC models you know apart from these two which you have mentioned?

#47 vijay

>>Its reall nice,i can understand how to write a effective bug Report,but please can u send me Original Bug Report Template with some examples.. i am working as a Manual tester..


till now which template you were using? you were not able to communicate properly with developers with your template? because many organizations use many template formats.

#48 Min

1 .do we have any standard test template for testing component/ classes? we have any standard test template for testing internal window application?

#49 Praveena


Really ur material is good … excellent

#50 susan

How to write the bug report?
I could see lot of times the testers starts with the objects first then subject, like “if user enter something page crash ” is it right? or subject first then object, like Page crash on ‘event’ when user enter something” which approach is right? please comment me…

#51 Nikhil

To Priya K,
U can get project easily for ur MBA. Contact me. Thanks,

#52 S R


can anyone pls suggest me for which tool to start with.
I m having 2 yrs exp in manual, now i want to learn tools.


#53 George

VSTS is the best tool for performance testing and QTP for functional testing.

#54 phalguna

Its reall nice,i can understand how to write a effective bug Report,but please can u send me Original Bug Report Template with some examples.. i am working as a Manual tester..we have no particular template in our company so please Help me this is my mailid

thanks for Advance

#55 Kavita


this article is really helpful. Can anyone please explain how to write bug report by some examples. like above asked for sql based project example. it would be better if u post it in this knowledgable and helpful site. if not comfortable my email id is


#56 mani

i need lot of help in testing can any one guide and share their respective knowledge with me

my id is

#57 mani

hi kavita can we chat in gmail to know more about testing and share knowledge

#58 VijayD

I feel attaching screenshots of the BUG is very important in Bug reporting.

#59 AJAY

Hi, i came to know alot of things about bug reporting.
thank q and the importace of screenshots.


Hi All,

On seeing many requests, I feel that the below one would be helpful to you all.

Lets assume in your application you want to create a new user with his/her information, for that you need to logon into the applicataion and navigate to USERS menu > New User, then enter all the details in the User form like, First Name, Last Name, Age, Address, Phone etc. Once you enter all these need to click on SAVE button in order to save the user and you can see a success message saying “New User has been created successfully”.

Now you entered into your application by logging in and navigete to USERS menu > New user, entered all the information and clicked on SAVE button and now the application creashed and you can see one error page
on the screen, now you would like to report this BUG.


Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID : It will be automatically created by the BUG Tracking tool once you save this.
Area Path: USERS menu > New Users
Build Number:/Version Number 5.0.1
Severity: HIGH (High/Medium/Low)
Priority: HIGH (High/Medium/Low)
Assigned to: Developer-X
Created By: Your Name
Cerated On: Date
Reason: Defect
status: New/Open/Active – Depends on the Tool you are using
Environment: Windows 2003/SQL Server 2005

Application crash on clicking the SAVE button while creating a new
user, hence unable to create a new user in the application.

Steps To Reproduce:
1) Logon into the application
2) Navigate to the USers Menu > New User
3) Filled all the fields
4) Clicked on Save button
5) Seen an error page “ORA1090 Exception: Insert values Error…”
6) See the attached logs for more information
7) And also see the attached screenshot of the error page.

Expected: On clicking SAVE button should be prompted to a success message “New User has been created successfully”.

Save the defect/bug in the BUG TRACKING TOOL.


#61 Sangeetha


Thanks for the worderfull document, which could help all the freshers(tester) to give a very good report. and this could help to increase there Confidence level.

#62 hareesha

its very nice article and very usefullllllll.
thank u very much.

#63 Storm


i read all the bonus points to write the effective bug report and i totally agreed with u except one……….

here u say before writing the bug report we reproduce it three time but in some case we found the error in single time and in future it will not generate…….then what we will do with these type of bugs……….

e.g. in some case while testing we found the scripting error but if we try to reproduce it then we may or may not get it again.
then I want to know in this case what we will do.


#64 senthilkumar

Hi I am a beginner in testing. This article very very useful for me.

#65 Thanigam


I like your explanation for testing concepts, could you mail me the current updates in testing concetps.


#66 selvam

Hi Friends,

Currently i am working in Non-IT field and planned to switch my career to testing.I had learned the basics of testing,and now i am very eager to learn testing practically with real time projects.
If any one interested to teach testing personally with real time projects , i will be more grateful, or else show me the right place in chennai.
Thanks & regards

#67 prasad

bug reporting processes is very nice given by you.

thanQ very much

#68 upender reddy


i like your concepts,
thak you very much.

#69 sarang shinde

how to write a good bug report

#70 viji


I am testing the Web Applications. I am manually preparing the Bug Report. can anyone suggest me which is best Bug Tracking Tool. (Open source Bug Tracking Tool).

with regards,

#71 Abhishek Kumar

In a day how many test cases you write in your company.
In a day how many test cases you have to write.

#72 Abhishek Kumar

In a day how many test cases you can write in your company
In a day how many test cases you have to write.

#73 ashwani sharma

writing of test cases depends upon the type of task if the task is typical then u have too think too much about the various conditions.

remember one thing better the test cases and the planning best is ur testing and for both of it u have too think deeply.

#74 abhaya

how do we deal with the bugs which are reproducible but end user has no control on reproducing them, for example there is some test requested and a test number is generated ….. 1 request opens one test # and is shown to end user …. but actually some times 2 test numbers are generated and the other one is hidden.

#75 Abhishek Kumar

Thanks ashwani

#76 Abhishek Kumar

Hi friends plz share ur experience.

How can I write a Test Scenario for the particular module. Plz understand me with the example?

#77 Abhishek Kumar

Hi friends plz share ur experience.

What is the diference between Test Scenerio & Test Case. Plz understand me with example.

#78 I feel very good

I usually test by manual and write bug on program write mantis. I feel very worderful.
I want to learn to every body.

#79 Abhishek Kumar

Hi Vijay
& friends plz share ur experience.

How can I write a Test Scenario for the particular module. Plz understand me with the example?

#80 Abhishek Kumar

Hi Vijay
& friends plz share ur experience.

What is the diference between Test Scenerio & Test Case. Plz understand me with example.

#81 Praveen kumar

Its reall nice,i can understand how to write a effective bug Report,but please can u send me Original Bug Report Template with some examples.. i am working as a Manual tester..plz…

#82 Praveen kumar

plz.. send me the Bug Report

#83 Praveen kumar

sorry for writing wrong email Id My

#84 Hi Vijay

Its really good,
Pls mailme bug report.

#85 vasu

Hi everyone,
Can anyone explain me to how to use Excel sheet with common repository as a bug tracking tool. Please help me out as I am new to testing job.

#86 lalit

Its really good, I can understand how to write a effective bug Report,but please can u send me Original Bug Report Template with some examples.. i am working as a Manual tester..plz…

#87 veeraiah chowdary.k

Its really good, I can understand how to write a effective bug Report,but please can u send me Original Bug Report Template with some examples.. i am working as a Manual tester..plz…

#88 karthik

Hi vijay,

how do I write the test case i.e. if the parameter fields are selected in browser and the reports are generated in excel… is there any link for this type of scenarios…

Thanks in advance,

#89 premKumar

Hi Vijay,

I am doing testing course.Do u have any sample test cases like test case scnario.Can you please send to my mail id


#90 Minhaj S

The article is really very helpful for all beginner testers.

#91 Rahul Mishra

Can anyone send me effective bug Report, and Bug Report Template with some examples..
I will be very thankfull to you.


#92 Rahul Mishra

Can anyone send me effective bug Report, and Bug Report Template with some email id is
I will be very thankfull to you.


#93 Shyam Singh

I am a developer of orcle based application. Now want to swith to testing. Can you help me in this regards.
I need some resume specially for testing.
Can my last experience help me in testing??
Thanks in advance.

#94 hari

This is very much useful. Keep rocking.

#95 resh

hii 2 all….
can som1 provide me d steps 2 install bugzilla(open source defect trackin tool) on windows….

my id is:

thnx in advance..

#96 Mohan

This is very nice and it covered lot of points

#97 manisha khobragade

Hi all,

Please suggest me any ideal Bug Tracking Tool or Bug Report……….

#98 Anagha

Can you send me the book on “”?


#99 seryein


#100 Mohammed Shahnawaz


I read through your article and found it to be very informative to work professional with a aim
to achieve quality, requesting you to send me a copy of the bug report on my mail id

Thanks in Advance.

Warm Regards,
Mohammed Shahnawaz

#101 sundar

hi vijay,
r u working in testing field? one week before i have been entered in testing field. can u send one model test case report. i am also prepared test case report. if u send it can very helpful to my work i hope u will do this

with regards

#102 neetu

very gud material

#103 Devi

Its very good.

#104 Roman Ahmed

nice guideline for any new tester……thank you

#105 Anup

hi this is Anup here.
Now i am working in E-Learning Industry, i am a QA-Tester. Maximum time i was doing Manually testting. how i am create a Good Bug-Report…. any format in Excel files..Please send me.
thank you.

#106 Anup

Hey hi all,
Please give me any Free tool………so we r using our company..actually my companies setup is very small….just 20-30 people… that will help us lot…..please suggest any Free Bug-Tracking tool.
thank you

#107 Nutty

I think Bugzilla is free for download and usage. Just try out this link ‘’

#108 Gopal

This is really nice one.
I learn lot from this.

#109 Gautam

I need some help. Could you solve this query i got this query the other day. Any help would be appreciated

Write down any potential problems or omissions from this

Fault Log

Fault no: 278 Environment: Windows 98
Priority:3 Tester:Author
Application: Web testing

When i log onto the screen DF342 I should be able to delete records. However when trying to delete records an error message appears telling mw that im not authorized

25 Aug: Programmer: Security needs to be setup providing access to the delete facility- No error

26 Aug:Tester: We had Security up and it doesnt seem to work- I have reopened this fault

#110 Sreenivasa

I think this bug report is vary big, the tester doesn’t have that much of time to prepare this.

#111 Sreenivasa

I think this bug report is vary big, the tester doesn’t have that much of time to prepare this. but the theory concepts are good

#112 Abhijit Mishra

Ohh…Its excellent…Thankx for adding this in this forum…It really gives a good idea about preparing a bug report..So thanks again…

#113 hitesh

hi Abhijit , this is normal bug report format , don’t be more excited . This bug report is not enough for CMM level company.

#114 Gautam

You guys, the reason i put this report was to get the solution for the fault log. Any response would be appreciated.

#115 Samy

Can anyone send me effective bug Report, and Bug Report Template with some email id is
I will be very thankfull to you.


#116 Sunil

It’s really nice article.

#117 pengli

Hi Vijay
It’s very good
Can u mail me the bug report ?


#118 Rahul

I liked this article… thnks for it.
If u can post some Bug report then it will be very good.

Again Thnks…

#119 sandrar

Hi! I was surfing and found your blog post… nice! I love your blog. :) Cheers! Sandra. R.

#120 madura

Hi all,

I have been asked one question in interview Regarding Test Director. Its as below.
How do you create a defect Report in Test Director, which must contain your Product name, Module name, Release name/ number, How many bugs you got, how many are fixed, how many are remaining and etc?


#121 Govardhan Reddy M

Dear Ms.Madura (#127),
Very nice to see your question. This question sounds that, The interviewer wants to know, “How well we (test engineers) aware of Quality Center (Formerly Test Director) Application features?”

But cleanly speaking, We won’t do that task(s), Wherein Team Lead / Manager / Client will do that often (whenever required/needed).

Fine, But the above lines are not good reasons to disclose with the interviewer. Why I said the above lines because, Not only you, But most test engineers concentrate on reporting bug, or looking for a bug status, or change the state of the bug etc., rather testing (analyzing) the Test Director itself.

What I mean is, We least bother about the rest of the features of this application. Its why, We are unable to answer such kind of questions – if asked by the interviewer(s).

Let me explain – “How that will be done?”

After succesful login to the Quality Center (don’t confuse, Quality Center is formerly known as Test Director). Now its Mercury Quality Center 9.0 and also HP Quality Center 9.2

1. At the left side, We see Releases, Requirements, Test
Plan, Test Lab (in vertical view). Adjacent to
Releases, We find Tests, Edit, View, Favorites,
Analysis (in horizontal view).

2. Click on Analysis.

3. Under Analysis, Click on Reports.

4. Under Reports, Click on Standard Test Planning

5. If any pop-up appears, Just allow blocked content (
to Run Active-x controls).

6. After Clicking on Standard Test Planning Report, A
report gets generated and will be displayed for you
(of course in the same current web page only but not
in a new browser window, or in a new browser tab),
Wherein you see some icons on the top of the page.

7. Don’t worry about the report that got generated. Just
ignore that.

8. Just click on the last icon which is “Configure Report
and Sub-Reports.”

9. Once you click on that icon, Again one page will get
displayed, Wherein we can see two filter icons. One
is for “filtering” and the other is for “clearing all

10. “filtering” icon looks like just like plain filter
and “clear filetering” icon will have a red mark at
the end of the filter / bottom of the filter / neck of
the filter. (Why I said because, Here if we keep
cursor on those two icons, to find out, what is what
for, the text is not getting displayed (which is a
bug), Its why)

11. Just click on first filter icon (for filtering).

12. A window will pop up with filter conditions and
displays us the below fields for filtering.
Estimated Dev Time
Estimate Time
Execution Status
Original ID
Previous ID
Test Activity Type
Test ID
Test Name

13. Just go the desired field for which we need to filter
(In y(our) case, Profuct Name, Module Name,
Release Name, Release Number, Designer (How
many bugs you (test engineer or may be developer,
Because under “Designer” field, next to this, If we
click on the horizontal line (adjacent to the Designer
field), Both test engineers names and development
engineers names will be listed in which we need to
select)), Status (How many are fixed), ……. How
many are remaining (why I mentioned “…..” is
because, the fields are predefined as well as user

So, Its up to the requirement of the client/company
in chosing (defining) the fields.

14. Go to the desired fields, Click on the line adjacent to
that particular field, Where in we see, A box
with “…” , Just click on that box and select the
appropriate “fields”.

Note: For a single filter, We can give one or more filters using “And” “or” etc..

Note: We can go for filtering “n” (any) number of filters (provided that those fields are defined).

Note: A report which gets generated once we click on
“Standard Test Plan Report” consists on no filters.

Based on the above generated report only, We are going to filter as per our needs/requirements.

15. Once we are done with filetering, Just click on “OK”
button on the popup window. The popup window will
get closed.

16. Then Click on “Apply” on the bottom of the page.

17. Report gets generated as per the filteration.

18. Click on “Save” icon (the third icon from left).

19. Under that, we see “Current Page” and “All Pages”.

20. Select “All Pages”

21. A window will be displayed for us to chose “where
to save the file?”

22. Just chose the path “where we need to save”.

Note: File format is either .mht (web archive) or .htm
or .html or .txt

Note: By default the format of the file is .mht.

Hope now you are cleared – I guess!

Hope you are an experienced test engineer, Because such kind of questions won’t be asked for test engineers who are having little experience (like 1 to 3 years but not more that 3 years)!!!

Have a great day ahead!

Govardhan Reddy M,
Software Test Engineer,
“Law of win says, Lets not do it in my way or your way,
But lets do it in the best way”.

#122 madhura

Hi Govardhan,

Thanks a lot for your detailed answer.
I have used TD one year back. is this filtering available in TD also. right now we are using Bugzilla in my current company..
please let me know is this feature available in TD7.0 or not.


#123 Govardhan Reddy M

Dear Ms.Madhura (Rohini) (#129),

Its pleasure to share my knowledge/experience with you. You are welcome.

Fine, Before answering to your question(s), Let me apprise (make aware of) you few details.

1. Test Director and Quality Center are same.

2. Version of Test Director 8.2 onwards was known as
Qaulity Center.

3. Latest version of Quality Center is 9.2 (HP)

4. Latest version of Quality Center is 9.0 (Mercury).
Note: Not very much sure about this Mercury Quality
Center version.

5. Quality Center is more advanced when compared to
Test Director.

6. Test Director is often referred to TD.

7. Quality Center is often referred to QC.
It may be Mercury QC or HP QC.

Now let me answer your question(s).

1. Yes, Filtering is available in TD also.

2. Yes, Filtering is available in TD 7.0 also.

Some additional information:

1. TestDirector is a test management tool. In TD one
can write manual and automated test cases, add
requirements, map requirements to the test cases
and log defects.

2. Bugzilla is used only for logging and
tracking the defects.
Migration from TD 7.2 to QC 8.0

There is no risk of losing the data during the migration process. One has to follow proper steps for successful migration.

No “please” is required.

You are welcome.

Have a great day ahead!

My suggestion to you, During your free time in office, Just keep doing R & A (Research and Analysis) on the tool on which you are working (say here, Bugzilla), You’ll come to know “what is what of that tool” or ” what more can we do from that tool” etc.,

“Incorrect assumptions lie at the root of every failure, But have the courage to test your assumption.”

Good luck.

Govardhan Reddy M,
Software Test Engineer,
“Dare to admit mistakes, But learn from them”.

#124 santhi

I want to know “What is the meaning of Duplicate defect?” and ” what is backward tracebility?”please give me the information asap.

#125 Govardhan Reddy M

Dear Ms.Santhi (#131),
Duplicate is one of the state of the bug when it moved to Documentation.

Bug will be moved to Documentation state during the following situations.

1. Invalid
2. Duplicate
3. Deferred
4. As Designed

1. Invalid: Its not a bug (this happens due to mis
understanding of SRS by the test engineer).

2. Duplicate: This bug has been already raised by some
one (test engineer, customer from field) in
earlier version/release or may be in the
current release/version.

3. Deferred: This is an enhancement which may going to
cover/fix in the forth coming (future)
release(s). This state often referred to be
as “Postponed” some times.

4. As Designed: This means that, The behaviour of the
DUT/SUT/AUT is correct as per the

Last Byte:
First state of the bug is “New”.
Then it will be under a state of “Open of this Defect: Yes/No”:

If “No”, Then it will be moved to “Documentation” state which reflects either “1/2/3/4”.

Hope now you are cleared – I guess!

Coming to backward traceability, I’ll get back to you at later point of time.

Govardhan Reddy M,
Software Test Engineer.
“Law of win says, Lets not do it in my way or your way,
But lets do it in the best way”.

#126 Shivshankar

It’s really good .

#127 Prasanta

This is really a Good Article. Thanks

#128 Prasanta - Kolkata

Can somebody help me to suggest few Testing Certifications available in India. Please write the URL’s for the same. Thanks

#129 rajbabu

pl send health care domain bug report

#130 rajbabu

pl send health care domain bug report to my id

#131 sreevani S

Really Good information.. Govindan
I want to know about agile testing.. where it will be used??

will u give me some information on this!!


#132 shrikant

What is the todays highest salary for software testing in india and other country?for 4 to 5 year experiance person.

#133 sandeep marwaha

my main problem is writing an essay and reading passage .please tell me how to remove this problem .

#134 sandeep marwaha

actualy sir i m student of commerce , my main focus in accounts , economics , business , etc. .in between i ignore our communication skills , so at that time i have create so many problems in communication skills. so please give me advice how to improve our communication skill in short passage of time .

#135 SD

One more bug reporting process using Visual Studio- TFS(Team Foundation Server)
1. Assume your team contains 8 members (Tester, QA Lead, 3developers, Dev.Lead,Project Lead, BA(Business Analysist)
2. You all have access to TFS
3. Tester reports a bug using TFS (Say bug no 123), there is a HISTORY tab in TFS will track all the changes made by any of the team member if there are any changes performed on 123.
4. After reported the bug (123) the default ‘Status’ of the bug will be TRIAGE.
5. There will be one more option ‘OWNER’ which contains default ID of QA Lead
6. Once tester submitted the bug with triage status it will automatically assigned to QA Lead
7.QA Lead will validate the bug and will change the status to ACTIVE (from Triage) if 123 is really a bug
8. If he / she feels it is really not a bug (may be setup issue, environment problem,calculation error, misunderstanding) then he/ she can close the bug in the begening stage it self
9. While QA Lead changing the status to ACTIVE he/she will ASSIGN the bug to DEV.Lead.
10.Dev Lead will have an idea about the bug and he may know the developer who coaded the form (on which bug 123 was reported) and he will Assign to Developer1
11.Developer1 will change the status to In-Progress
12. Again developer will look deeply in to the bug and if he feels/ having any doubt then he may consult Business Analysist to know more about the functionality
13. If Developer / BA will prove it is not a bug he can close the bug with reason (Not an Issue / As Design)
14. Developer accepts that 123 is a bug then he /she starts fixing(Code Changes) the bug
15. Once he/she fixed the bug then change the bug status to ‘System Test’
16. New build dyployed into server with all code fixes
17. Tester will again test the reported bug (123) on newly released build
18. If the bug is really fixed tester will change its status to RESOLVE/CLOSED with reason TEST PASS
20. If the bug is still occurring then he again change the status to ACTIVE with reason TEST FAIL

#136 padmaraj

its really fantastic,and very easy to understand.


#137 Barry

We are using in the last week a tool called informup and all fields and your recommendation in this article exist in this tool. I think it ivery helpfull

#138 Raj Pawar

Hi Vijay

I want exel sheet of testing(Manual),test cases,test plan..Functional Testing…with eg..

With regard
Raj Pawar

#139 Nitin More

Its very useful information…..keep it up..

#140 Uma


can any one send me the Bug report template ASAP

my mail id is

#141 Archana

I find this article very helpful and will consider it as a guideline for my report as a Tester.

#142 Ciciya lal

Thanks a lot for your detailed answer.
I have used TD one year back. is this filtering available in TD also. right now we are using Bugzilla in my current company..
please let me know is this feature available in TD7.0 or not.



#143 Praveen

Very useful article. Thanks.

#144 ravindra kumawat


can you discribe the example of test case and test plan written in excel sheet

#145 Pilu

Hello,i am new to the testing i dont have any idea how to write test cases and bug report,initially to begin with ui test will be given to me,how should i proceed?pls help and initially should i join some course or is there any mateial available?

#146 Pilu

What is test plan?For what purpose is it written?

#147 Mayasen

Hi Pilu, #153/154

Test Plan is the document which carries all data about your complete STLC (Software Testing Life cycle).

A typical test plan should contain,

# Introduction about project & testing
# Test Plan Objectives
# Scope
# Test Strategy
~ System Test
~ Performance Test
~ Security Test
~ Automated Test
~ Stress and Volume Test
~ Recovery Test
~ Documentation Test
~ Beta Test
~ User Acceptance Test
#Environment Requirements
# Test Schedule
# Control Procedures (Reviews, Bug Review, meetings, Change Request, Defect Reporting)
# Functions To Be Tested
# Resources and Responsibilities
# Deliverables
# Suspension / Exit Criteria
# Dependencies
# Risks (Schedule, Technical, Management, Personnel, Requirements)
# Tools to be used
# Support Document details
# Approvals

#148 Viju

Hi Vijay & Friends,
I want to do a testing project in erp domain – HR module. Can u please guide me how i have to go about it?
Wat is the work flow that has to be used for this purpose?
Thanks in advance

#149 Viju
This is my email id. Any suggestions in this regard
would be greatly appreciated.

#150 Unus

really awesome it helps a lot

#151 sourav462

What are the general tools used for bug reporting, also how to get an overview of them?

#152 Mayasen

Very frequently using bug tracking tools were Mantis, Bugzilla.. (Both are open source tools).

#153 vijaykumar

can you mail me personally to the a bug report to my mail id is
thank you

#154 pawan

i am pawan working as a software test engineer. your report is really good .

#155 Bhushan

Hi Vijay ,
Ur report is nice n definately it will help me
please mail me bug report , defect life cycle and other required material which is ask in interview


#156 black celebs

Sign: wdpad Hello!!! vudww and 7531kzxqhhcchk and 4881 : I like your blog. cool post!

#157 Ajwan Arouje


This is very intersting and useful for me as am a fresh tester…
It will help me to grow further..

Thanks once again.

#158 Karthik

Mr.Govardhan Reddy

i have completed MBA(SYS) and certified software testing
course also. i have experience in Non TESTING Field. i want to switch over to testing field. i have theoretical knowledge but i need some real time testing knowledge.

can u help me?

can any sample testing projects for me, if u sending it
will really literal help for me..

Expecting your favorable reply.

my id is


#159 Mahesh

Hi vijay,
ur points are valuable. It is better if we also present the same in a graphical way.

#160 Venkatesh

Hi Vijay

Very useful information

#161 shanti

I find this article very helpful and will consider it as a guideline for my report as a Tester.


#162 MooHero

Very useful article


#163 bipin

u can visit for other tseting questions

#164 Achyut Aradhye

Nice info. It’s worth to understand the quality bug reporting in testing practice

#165 raju

hi all
nice to see this website n discussion n its really worth.. thanks to all seniors who sharing their knowledge here really hats of to ur work..
one request plz can anybody tell me wt is test process,test methods,test methodology,test procedure,test plan differences plz plz …
please send ur answers to my mail i.e

#166 Karthikaa

Hi All,

This is Karthikaa, i am working as Manual Tester. Plz some body help me how to do Documentation. Your suggestions are regretful. Thank u.

#167 Shraddha N.

Hi Vijay sir,

Very useful information & points are explains.. here…
after reading this article…I want to change…my job profile…as software Translator to Software tester…


#168 Sohail

Thanks for your input.
But Here on this Site. we Expect it Better.
Lets Stick to basics of Effective Bug Reporting and
try to invent new ways, using this site.
Good Try Dear.


#169 Pratibha


Its a very nice article. Specially the points which you have mentioned under Severity.
One question- which are the mandatory points while writting the bug report?

#170 chithra reddy

hi its really meaning full.. thankz a lot bye..

#171 Manish

This was very helpfulll……
thanks a lot

#172 Sandeep

Its a very nice article..

#173 ETS

This is great! It is my first post in this website and wont be my last! If i find more useful information i will make sure to post. I have been throught many websites that i lost count but this i must say is by far the best, comprehensive and easy to understand. Great Job!

#174 saurav

It’s helpful to me.

#175 saurav

Actually I am doing a project on Bug tracking system and i get help from this site.

#176 Rupesh Mandhare

The way mentioned all testing methods and portrayal which really helpful for anyone.

I wish you to all please keep an using this website for rising software testing awareness

#177 Dhanashree

This site really helpfull for freshers as well as experienced
I want to know about detail for how the Testing process followed in company?

#178 sree

hi ,

can u share details of that website

#179 Praveen

can you please provide the bug templet

#180 NITIN

hiiiiii thanks for the information its really helpfull lots of things i got it from above. so thanks u very muchhhh.

#181 vandana


I am manual tester gradually learning new things to become a proper tester .My main problem is that i am not able to explain the bugs to the developers in brief. I am in very much need of bug report template and testcase template.Please help me for the same to make successful in my further career.

#182 Basith Shai

Very informative,helpful tips

#183 Ratz

Excellent work vijay,

It’s the best website for software testing.. :)


#184 Joel Montvelisky

Good post. I would only add, that in order to know your bug well (and hence write a good bug report), you need to know the product well. IT’s really important, and seems trivial, but you’ll be surprised at how many testers don’t know the software product before they test it.

All the best,


#185 Yordys Valenzuela

Amazing work. definitely i will use this article for a presentation in my QA group. I want they to know how to create good bugs.

Thanks again.


#186 Samu

Good website. All post very useful. I’m following this website for my testing process.Learnt lot of things about testing using this website.

GREAT JOB!!!!!!!!!!

#187 laxmi

thanks, really it is very usefull for me
how to write test cases with examples .as i feel difficult for writing test cases please inform to my e-mail ID

#188 Krish

Thanks for good info

#189 mahalakshmi

could you please provide me the steps to prepare the checklist and test cases before testing?

#190 mahalakshmi

please provide ma a sample test case and check list


It is a very use full report for fresher

#192 Abdul Kader

This tips are really usefull to me.

#193 shalini

its very useful. i learned more.

#194 thenmozhi

Its very useful artical

#195 thenmozhi

Its very useful to me……,

#196 shalini



Hi, its very useful to me.

Thanks For your valuable information

#198 sneha

very useful post because its providing good knowledge about writing a bug report …………..impressive

#199 khan

Good stuff for the beginners and intermediate testers

#200 tintin

Very comedy comments… :)

#201 Santhosh Tuppad

This might help you in better bug reporting. Crash Course on Bug Reporting –

— Santhosh Tuppad

#202 apurva verma

Hi All,

This is Apurva, i am new in software testing.This article is really very useful. Plz some body mail me the complete testing process how it ia done practically as I only have theoritical knowledge.I am in urgent need of it. Thank u.
My email addresss is:

#203 ankit

Hi , Im Ankit, can any one send me the names list of bugs generally found while testing a game? I know only a few names like graphical bugs, freeze bugs etc.,
Plz mail me the list if u knw

#204 sree's

good article..
can any 1 explains the difference b/w userinterface & functional testcases?

#205 Rishikesh

Very help ful thanks for sharing…!!!!

#206 sourabh bhave

Really nice information posted which will fresher as well as experienced people to get to know well with bug reporting

#207 janardhan

Can any one give me the examples of:
1) high severity-low priority
2)high severity-high priority
3)low severity-high priority
4)low severity-low priority

#208 Satish

Lot of testing learned @ ‘’; thanks Vijay….

Also, I’m looking for a brief article on test scenario…

#209 Satish

I’ve subscribed for news letter, but need this post. Can you please mail this post to me?

#210 chirag gajjar

nice report..

#211 Satish

good one

#212 shankar

please can you mail me the bug report


Whatever truly moved you to compose “How to write a good bug report?
Tips and Tricks – Software Testing Help”? Igenuinely appreciated
it! Thank you -Chassidy


I personally blog as well and I am posting something very similar to this specific post, “How to write a good
bug report? Tips and Tricks – Software Testing Help”.

Would you care in case I actuallyutilise a number of your
personal ideas? Thanks ,Muhammad

#215 sarvesh

Hi Vijay,
This is sarvesh,i m Fresher. please help me,
can you mail me personally to the a bug report to my mail id is
thank you

#216 sarvesh

hi… frnds please help me send me……
Can anyone send me effective bug Report, and Bug Report Template with some email id is
I will be very thankfull to you.


#217 ranaji

i also like your post so well please help me i want to get simple bug template for functional and regression test.


#218 SAM

The info is vry clear,effective and useful…..will someone send a sample bug report plz ?

#219 SAM

Hi…Plz send a sample bug report to the following mail id.


#220 Chris Kerr

Great article. One thing that I add to my defect write up is a severity justification if I’m giving the bug a Sev 1 or 2.

#221 pritam

Thanks ……for nice Experiment.

#222 Srinivas

Nice article, Thanks for posting this article. It is very useful for testers………….

#223 smitha

good artical

#224 Priyanka

Thankyou so much. Get to know so much of knowledgeable stuff through your articles

#225 Jayashree

Nice one thanks.

Jayashree Patil

#226 Jay

Thank you for very interesting and helpful article. can you please give us a link for the template of the Report bug? how it look like.

Thank you, more power!

#227 Ashwin

hi friends,
how to write a letter to manager when we got new bug?

Thanks and Regards

#228 Sujana

This is very helpful article

#229 pradeep

hi all,

this is really nice article……………thanks for


#230 vijayashree


Let me know E-learning domain testing process.

#231 Khan Mohammad

I really appreciate you! It was very useful, specific and very clear. Thanks a lot. wish you all the best

#232 shahi kant

hi this site helpfull to my self

#233 Sari

Rules and tips are very helpful.
Thank you about your essay

#234 nilu

I read Bug Report Article it is very good.could u pls give an original bug report?

#235 Shrishail

We have one form in that we have around 4 fields and all fields have same should i report one bug or 4 different bugs for 4 fields

#236 mahesh

it was very beneficial and also develop the knowledge.

#237 Navneet

Can you mail me the bug report format sample on

#238 Shalav Garg

I really appreciate you! It was very useful, specific and very clear. Thanks a lot STH. wish you all the very best.

#239 krishna

in our company we are using using excel as bug report.In Bug Report(excel sheet)Is any need to maintain relationship with requirement specification document/test case document .

#240 Minh Nguyen

Nice article ! Thanks for sharing ^^

#241 chinmayee

This article is very nice…Can u please send me the bug report format…mail

#242 Sourabh

I am having 2 years of experience in manual testing. Now I want to go ahead with automation testing to enhance my career. I am thinking about 2 tools that are Selenium and QTP. Which tool should I learn between two to achieve more growth in my career?
Expecting reply asap.

#243 Abhijit


i have certified software testing
course also. i have experience in Non TESTING Field. i want to switch over to testing field. i have theoretical knowledge but i need some real time testing knowledge.

can u help me?

can any sample testing projects for me, if u sending it
will really literal help for me..

Expecting your favorable reply.

my id is


#244 pranita

hello sir, can u send me bugs report format on my email id??
my id is

#245 Ravella Baji

Thank You ,Really Helpfull….

#246 akshat

Very Helpful information

#247 Shashikant Berad

Can anyone send me effective bug Report, and Bug Report Template with some email id is
I will be very thankfull to you.

#248 Chethana Mahindapal

Simply grate.

#249 Miki Freeman

This could have used an editor (and since I mentioned that I’ll likely make an error here…)
I was looking for some information on writing effective, concise bugs, and in the second paragraph I see:
“stating as irreproducible. This can hurt testers moral and some time ego also.” sigh. (morale and sometimes…)
However, reading the rest of the paper, I see a good basic breakdown of writing a bug. Something to keep in mind is some people (especially QA professionals) might not have read past the second paragraph.
Good material, just needs a bit of tweaking.

#250 sam blogest

Really nice information. It will help freshers as well as experienced people
to get to know bug reporting well. All the tips you have provides are very

#251 Jithesh K K

Nice information.

#252 Chandrashekahr M

Hi Vijay,

its Really a Very very Good Artical,Quickly every one catch this scenario easy.

Am really Telling When I Join As Qa No one Suggesting how to Handle the Bug But now i can easyly Handling.


#253 Malar Pretty

nice information.

Leave a Comment