How to write a good bug report? Tips and Tricks

Why good Bug report?
If your bug report is effective, chances are higher that it will get fixed. So fixing a bug depends on how effectively you report it. Reporting a bug is nothing but a skill and I will tell you how to achieve this skill.

“The point of writing problem report(bug report) is to get bugs fixed” – By Cem Kaner. If tester is not reporting bug correctly, programmer will most likely reject this bug stating as irreproducible. This can hurt testers moral and some time ego also. (I suggest do not keep any type of ego. Ego’s like “I have reported bug correctly”, “I can reproduce it”, “Why he/she has rejected the bug?”, “It’s not my fault” etc etc..)

What are the qualities of a good software bug report?
Anyone can write a bug report. But not everyone can write a effective bug report. You should be able to distinguish between average bug report and a good bug report. How to distinguish a good or bad bug report? It’s simple, apply following characteristics and techniques to report a bug.

1) Having clearly specified bug number:
Always assign a unique number to each bug report. This will help to identify the bug record. If you are using any automated bug-reporting tool then this unique number will be generated automatically each time you report the bug. Note the number and brief description of each bug you reported.

2) Reproducible:
If your bug is not reproducible it will never get fixed. You should clearly mention the steps to reproduce the bug. Do not assume or skip any reproducing step. Step by step described bug problem is easy to reproduce and fix.

3) Be Specific:
Do not write a essay about the problem. Be Specific and to the point. Try to summarize the problem in minimum words yet in effective way. Do not combine multiple problems even they seem to be similar. Write different reports for each problem.

How to Report a Bug?

Use following simple Bug report template:
This is a simple bug report format. It may vary on the bug report tool you are using. If you are writing bug report manually then some fields need to specifically mention like 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 operating systems where you found the bug. Operating systems like Windows, Linux, Unix, SunOS, Mac OS. Mention the different OS versions also if applicable like Windows NT, Windows 2000, Windows XP etc.

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

Severity:
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 new feature or some enhancement in existing one.

Status:
When you are logging the bug in any bug tracking system then by default the bug status is ‘New’.
Later on bug goes through various stages like Fixed, Verified, Reopen, Won’t Fix etc.
Click here to read more about detail bug life cycle.

Assign To:
If you know which developer is responsible for that particular module in which bug occurred, then you can specify email address of that developer. Else keep it blank this will assign bug to module owner or Manger will assign bug to developer. Possibly add the manager email address in CC list.

URL:
The page url on which bug occurred.

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

Description:
A detailed description of bug. Use following fields for description field:

------------

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

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

The report types are typically:
1) Coding error
2) Design error
3) New suggestion
4) Documentation issue
5) Hardware problem

Some Bonus tips to write a good bug report:

1) Report the problem immediately:If you found any bug while testing, do not wait to write 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 chances are high to miss the important steps in your report.

2) Reproduce the bug three times before writing bug report:Your bug should be reproducible. Make sure 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 module:
Sometimes developer use same code for different similar modules. So chances are high that bug in one module can occur in other similar modules as well. Even you can try to find more severe version of the bug you found.

4) Write a good bug summary:
Bug summary will help developers to quickly analyze the bug nature. Poor quality report will unnecessarily increase the development and testing time. Communicate well through your bug report summary. Keep in mind bug summary is used as a reference to search the bug in bug inventory.

5) Read bug report before hitting Submit button:
Read all sentences, wording, steps used in 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 developer or to attack any individual.

Conclusion:
No doubt that your bug report should be a high quality document. Focus on writing good bug reports, spend some time on this task because this is main communication point between tester, developer and manager. Mangers should make aware to their team that writing a good bug report is primary responsibility of any tester. Your efforts towards writing good bug report will not only save company resources but also create a good relationship between you and developers.

For better productivity write a better bug report.



The Best Software Testing Training You'll Ever Get!

software testing QA training

234 comments ↓

#1 srianand on 09.18.07 at 8:51 am

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

#2 Thulasi Suresh on 09.18.07 at 12:24 pm

Hi
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 on 09.19.07 at 4:32 am

Nice One…………

#4 Mani on 09.19.07 at 5:25 am

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

#5 Poonam on 09.19.07 at 6:13 am

Hi
Its really helpful!!

#6 Vijay on 09.19.07 at 7:08 am

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

BTW,
Thanks all for the kind words.

#7 resna on 09.19.07 at 7:33 am

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 on 09.21.07 at 11:11 am

very Informative

#9 sdpanong on 09.21.07 at 1:57 pm

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

Thanks,

#10 prabhunair on 09.23.07 at 4:44 am

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 on 09.26.07 at 11:21 pm

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 on 09.28.07 at 7:25 am

@ resna – I have mailed you the bug report format. One simple report can also be viewed in comment section of post http://www.softwaretestinghelp.com/bug-life-cycle/

@ 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 on 09.28.07 at 10:49 am

Hi

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 on 10.09.07 at 3:16 am

Hi Vijay
Its very good
Can u mail me the bug report ?
grajeshkumar7@yahoo.co.in

Thanks

#15 varalakshmi prasanna on 10.10.07 at 10:55 am

hi,
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 on 10.14.07 at 9:17 am

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

Thank you

#17 kavitha on 10.14.07 at 2:29 pm

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

#18 Karthik on 10.23.07 at 3:32 pm

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

#19 vishala on 11.16.07 at 4:26 am

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 on 11.16.07 at 4:31 am

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 on 11.19.07 at 12:46 pm

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

Thanks
Suresh B

#22 zakir on 11.23.07 at 12:05 pm

@mohini

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

#23 Pravin on 12.14.07 at 7:12 am

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

#24 savithri on 12.18.07 at 8:31 am

Hi
this is so nice to read. can u mail me bug report
savithri_gudikoti@yahoo.co.in

#25 savithri on 12.18.07 at 8:33 am

can u mail me details on energy domain and what are the elements i need to cover
savithri_gudikoti@yahoo.co.in

#26 Gatari Mishra on 12.19.07 at 6:50 am

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…

Regards.

Gayatri

#27 Software Testing Help: Best software testing articles of 2007 on 01.07.08 at 12:24 pm

[...] How to write a good bug report? Tips and Tricks [...]

#28 How to get your all bugs resolved without any 'Invalid bug' label? on 01.23.08 at 9:26 am

[...] get his/her 100% bugs resolved. This requires bug reporting skill. See my previous post on “How to write a good bug report? Tips and Tricks” to report bugs professionally and without any [...]

#29 Kiran on 01.24.08 at 11:56 am

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

#30 rajjonnada on 01.29.08 at 6:49 am

Hi,

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 ?

#31 rajjonnada on 01.29.08 at 6:54 am

@mohini

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.

#32 rajjonnada on 01.29.08 at 6:55 am

@ vijay

can you mail me personally to the rajjonnada@gmail.com/raj_jonnada@yahoo.co.in.
thank you

#33 rajjonnada on 01.29.08 at 7:33 am

@vishala

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

#34 raja on 01.30.08 at 6:55 am

This article is fantastic vijay…

#35 raja on 01.31.08 at 11:41 am

@vishala

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

#36 raja on 01.31.08 at 11:42 am

This is by Mr. James Bach.

#37 suganya on 02.06.08 at 12:51 pm

Hi,
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

#38 suganya on 02.06.08 at 12:53 pm

hi,
u mail me in suganya.thirunavukkarasu@3i-infotech.com

#39 Gaurav Garg on 02.12.08 at 12:05 pm

Hi
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.

#40 Devendra sonpure on 02.26.08 at 8:56 am

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

#41 salman on 02.28.08 at 11:20 am

hi all
is Software engineer term can be used for qa

#42 salman on 02.28.08 at 11:27 am

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

#43 Pravin on 02.29.08 at 5:26 am

please mail me any bug report for sql based project.as next month i will be working on same,please.
pravin.mahajan1@gmail.com

#44 kathyayani on 02.29.08 at 5:55 am

please can you mail me the bug report

#45 kathyayani on 02.29.08 at 5:56 am

please can you mail me the bug report p.kathyayani@yahoo.com

#46 selvam on 03.05.08 at 1:20 pm

@vijay
Vijay you are doing simply the worthful job.really great

#47 selvam on 03.05.08 at 1:32 pm

Please can anyone send me the original bug report..
selvam.ba@rediffmail.com

#48 vijay on 03.06.08 at 10:14 am

>>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?

vijaysavalagi@gmail.com

#49 vijay on 03.06.08 at 10:20 am

>>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..

@suganya,

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.

#50 Min on 03.19.08 at 2:57 pm

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

#51 Praveena on 03.20.08 at 12:19 pm

Hi,

Really ur material is good … excellent

#52 susan on 04.10.08 at 6:09 am

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…
cheers
susan

#53 Nikhil on 04.13.08 at 9:14 am

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

#54 S R on 04.13.08 at 9:17 am

Hi,

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.

Sumit

#55 George on 04.16.08 at 5:22 am

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

#56 phalguna on 04.16.08 at 10:33 am

Hi,
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
s_phalguna@yahoo.com
Regards
PHALGUNA

#57 Kavita on 04.23.08 at 8:47 am

Hi,

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 kv.testing22@gmail.com

thanks
Kavita

#58 mani on 04.23.08 at 9:00 am

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

my id is saini.msmani@gmail.com

#59 mani on 04.23.08 at 9:02 am

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

#60 VijayD on 04.29.08 at 5:28 am

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

#61 AJAY on 04.30.08 at 10:21 am

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

#62 VIJAYD on 05.02.08 at 9:47 am

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 REPORT:

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

Description:
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.

Regards,
VijayD

#63 Sample bug report. How to write ideal bug report on 05.04.08 at 2:40 am

[...] If you need more information about writing a good bug report read our previous post “How to write a good bug report“.

#64 Sangeetha on 05.23.08 at 12:20 pm

Hi,

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.

#65 hareesha on 05.26.08 at 10:05 am

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

#66 Storm on 06.02.08 at 7:31 am

Hello……..

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.

Thanks

#67 senthilkumar on 06.11.08 at 7:28 am

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

#68 Thanigam on 06.11.08 at 10:24 am

hi,

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

regards,
Thanigam

#69 selvam on 06.11.08 at 2:02 pm

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
selvam.ba@rediffmail.com

#70 prasad on 07.03.08 at 7:27 pm

bug reporting processes is very nice given by you.

thanQ very much

#71 upender reddy on 07.10.08 at 12:28 pm

hi,

i like your concepts,
thak you very much.

#72 sarang shinde on 07.11.08 at 5:21 am

how to write a good bug report

#73 viji on 07.11.08 at 9:29 am

hello,

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,
viji

#74 Abhishek Kumar on 07.11.08 at 2:20 pm

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

#75 Abhishek Kumar on 07.11.08 at 2:22 pm

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

#76 ashwani sharma on 07.12.08 at 7:08 am

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.

#77 abhaya on 07.19.08 at 11:39 pm

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.

#78 Abhishek Kumar on 07.27.08 at 2:50 pm

Thanks ashwani

#79 Abhishek Kumar on 07.27.08 at 2:58 pm

Hi friends plz share ur experience.

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

abhishek.kur1@gmail.com

#80 Abhishek Kumar on 07.27.08 at 3:01 pm

Hi friends plz share ur experience.

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

abhishek.kur1@gmail.com

#81 I feel very good on 07.30.08 at 10:43 am

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

#82 Abhishek Kumar on 08.03.08 at 2:20 pm

Hi Vijay
& friends plz share ur experience.

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

abhishek.kur1@gmail.com

#83 Abhishek Kumar on 08.03.08 at 2:21 pm

Hi Vijay
& friends plz share ur experience.

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

abhishek.kur1@gmail.com

#84 Praveen kumar on 08.05.08 at 10:04 am

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…

#85 Praveen kumar on 08.05.08 at 10:07 am

plz.. send me the Bug Report
mailme.praveen@gmail.com

#86 Praveen kumar on 08.05.08 at 11:35 am

sorry for writing wrong email Id My mailID:mailmee.praveen@gmail.com

#87 Hi Vijay on 09.04.08 at 6:50 am

Its really good,
Pls mailme bug report.

#88 vasu on 09.12.08 at 8:08 am

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.

#89 lalit on 09.18.08 at 12:18 pm

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…

#90 veeraiah chowdary.k on 09.23.08 at 10:36 am

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…

#91 karthik on 09.25.08 at 8:13 am

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,
Karthik

Karthik@when.com

#92 premKumar on 10.01.08 at 6:41 am

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 prem.k74@gmail.com.

Thanks
Prem

#93 Minhaj S on 10.14.08 at 9:33 am

The article is really very helpful for all beginner testers.

#94 Rahul Mishra on 11.05.08 at 6:31 am

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

Thanx
Rahul

#95 Rahul Mishra on 11.05.08 at 6:35 am

Hi,
Can anyone send me effective bug Report, and Bug Report Template with some examples..my email id is
rmishra@digisigntech.com
I will be very thankfull to you.

Thanx
Rahul

#96 Shyam Singh on 11.06.08 at 10:00 am

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.
–Shyam

#97 hari on 11.14.08 at 9:51 am

This is very much useful. Keep rocking.

#98 resh on 11.20.08 at 4:10 am

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

my id is: itsreshz@gmail.com

thnx in advance..
resh

#99 Mohan on 11.20.08 at 7:30 am

Hi,
This is very nice and it covered lot of points

#100 manisha khobragade on 12.12.08 at 1:22 pm

Hi all,

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

#101 Anagha on 12.19.08 at 11:54 am

Can you send me the book on “anagha1007@gmail.com”?

anagha

#102 seryein on 01.16.09 at 9:55 pm

Reproducible: ALWAYS THAT IT BE POSSIBLE, PLEASE INCLUDE THE DATA USED FOR THE TEST, SOME BUGS HAPPENS WITH SPECIFIC KIND OF DATA.

#103 Mohammed Shahnawaz on 01.20.09 at 8:04 am

Hi,

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 iamnawaz@yahoo.com.

Thanks in Advance.

Warm Regards,
Mohammed Shahnawaz

#104 sundar on 01.20.09 at 9:23 am

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
sundar
sunaruna84@gmail.com

#105 neetu on 01.23.09 at 5:32 am

very gud material

#106 Devi on 01.31.09 at 10:26 pm

Its very good.

#107 Roman Ahmed on 02.02.09 at 9:33 am

nice guideline for any new tester……thank you

#108 Anup on 02.02.09 at 12:38 pm

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.

#109 Anup on 02.02.09 at 12:42 pm

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…..so that will help us lot…..please suggest any Free Bug-Tracking tool.
thank you

#110 Nutty on 02.03.09 at 5:00 am

I think Bugzilla is free for download and usage. Just try out this link ‘http://www.bugzilla.org/download/’

#111 Gopal on 02.17.09 at 11:22 pm

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

#112 Gautam on 02.20.09 at 7:05 am

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

Description
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

Response:
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

#113 Sreenivasa on 02.26.09 at 7:14 am

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

#114 Sreenivasa on 02.26.09 at 7:15 am

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

#115 Abhijit Mishra on 02.26.09 at 8:35 am

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

#116 hitesh on 02.26.09 at 9:20 am

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

#117 Gautam on 03.02.09 at 6:09 am

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

#118 Samy on 04.01.09 at 2:24 pm

Hi,
Can anyone send me effective bug Report, and Bug Report Template with some examples..my email id is
mr_gurusamy@yahoo.com
I will be very thankfull to you.

Thanx
Samy

#119 Sunil on 04.20.09 at 6:59 am

It’s really nice article.

#120 pengli on 06.09.09 at 4:26 am

Hi Vijay
It’s very good
Can u mail me the bug report ?
xuehubake@163.com

Thanks

#121 Rahul on 07.29.09 at 12:37 pm

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

Again Thnks…

#122 sandrar on 09.10.09 at 10:46 pm

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

#123 madura on 11.03.09 at 9:24 am

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?

Regards.
Madhura

#124 Govardhan Reddy M on 11.03.09 at 1:04 pm

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
Report.

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
fileters”.

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.
Automation
Creation
Designer
Environment
Estimated Dev Time
Estimate Time
Execution Status
Modified
Notes
Original ID
Path
Platform
Previous ID
Priority
QC_TCID
Regression
Status
Subject
Template
Test Activity Type
Test ID
Test Name
Type

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
configured.

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!

Regards,
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”.

#125 madhura on 11.04.09 at 7:35 am

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.

Regards,
Rahini

#126 Govardhan Reddy M on 11.04.09 at 8:23 am

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.

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

#127 santhi on 11.17.09 at 7:59 am

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

#128 Govardhan Reddy M on 11.17.09 at 8:36 am

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
requirement/SRS.

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.

Regards,
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”.

#129 Shivshankar on 12.17.09 at 10:29 am

It’s really good .

#130 Prasanta on 12.21.09 at 1:29 pm

This is really a Good Article. Thanks

#131 Prasanta - Kolkata on 12.21.09 at 1:32 pm

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

#132 rajbabu on 01.05.10 at 12:42 pm

pl send health care domain bug report

#133 rajbabu on 01.05.10 at 12:43 pm

pl send health care domain bug report to my id rajbabu_73@yahoo.co.in

#134 sreevani S on 01.06.10 at 11:46 am

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

will u give me some information on this!!

Thanks
sekharsreevani@gmail.com

#135 shrikant on 01.06.10 at 1:38 pm

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

#136 sandeep marwaha on 01.06.10 at 4:36 pm

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

#137 sandeep marwaha on 01.06.10 at 4:42 pm

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 .

#138 SD on 01.07.10 at 4:49 am

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

#139 padmaraj on 01.29.10 at 10:24 am

hi
its really fantastic,and very easy to understand.

thanks

#140 Barry on 02.26.10 at 2:02 pm

Recommedation:
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

#141 Raj Pawar on 03.08.10 at 11:37 am

Hi Vijay

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

With regard
Raj Pawar

#142 Nitin More on 03.09.10 at 7:23 am

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

#143 Uma on 03.19.10 at 11:42 am

Hi

can any one send me the Bug report template ASAP

my mail id is cumams@gmail.com

#144 Archana on 03.26.10 at 9:06 am

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

#145 Ciciya lal on 03.26.10 at 9:09 am

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.

Regards,

Ciciz

#146 Praveen on 03.30.10 at 9:13 am

Hi,
Very useful article. Thanks.

#147 ravindra kumawat on 04.01.10 at 5:39 pm

Hi,

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

#148 Pilu on 05.20.10 at 12:37 pm

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?

#149 Pilu on 05.21.10 at 10:21 am

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

#150 Mayasen on 06.04.10 at 4:41 am

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

#151 Viju on 06.12.10 at 5:26 pm

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

#152 Viju on 06.12.10 at 6:06 pm

lakshmi05.18@rediffmail.com
This is my email id. Any suggestions in this regard
would be greatly appreciated.

#153 Unus on 06.17.10 at 5:28 am

really awesome it helps a lot

#154 sourav462 on 07.07.10 at 2:24 pm

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

#155 Mayasen on 07.08.10 at 4:13 am

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

#156 vijaykumar on 08.03.10 at 6:42 am

hi,vijay
can you mail me personally to the a bug report to my mail id is vijaykumar.jalanila25@gmail.com
thank you

#157 pawan on 08.10.10 at 7:00 am

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

#158 Bhushan on 08.10.10 at 8:26 am

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
bwchaudhari@rediffmail.com

thanks

#159 black celebs on 08.10.10 at 6:33 pm

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

#160 Ajwan Arouje on 08.31.10 at 6:45 am

Hi,

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

Thanks once again.

#161 Karthik on 09.01.10 at 7:06 am

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 amarkeyan@yahoo.co.in

Thanks,
Karthik

#162 Mahesh on 10.08.10 at 4:04 pm

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

#163 Venkatesh on 10.08.10 at 4:11 pm

Hi Vijay

Very useful information

#164 shanti on 10.12.10 at 10:08 am

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

Thanks,

#165 MooHero on 11.12.10 at 12:33 pm

Very useful article

Thanks,

#166 bipin on 12.21.10 at 10:16 am

http://soft-engineering.blogspot.com

u can visit for other tseting questions

#167 Achyut Aradhye on 12.23.10 at 12:07 pm

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

#168 raju on 12.29.10 at 6:23 am

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 raju013@gmail.com

#169 Karthikaa on 01.10.11 at 11:00 am

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.

thugs2pals@gmail.com

#170 Shraddha N. on 02.01.11 at 9:39 am

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…

THANK YOU,
Shraddha

#171 Sohail on 02.11.11 at 11:32 am

Hi,
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.

Sohail…

#172 Pratibha on 02.20.11 at 5:22 pm

Hi,

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?

#173 chithra reddy on 03.01.11 at 12:54 pm

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

#174 Manish on 03.11.11 at 2:15 pm

This was very helpfulll……
thanks a lot

#175 Sandeep on 03.15.11 at 7:07 am

Its a very nice article..

#176 ETS on 04.10.11 at 5:17 am

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!

#177 saurav on 04.16.11 at 8:34 pm

It’s helpful to me.

#178 saurav on 04.16.11 at 8:36 pm

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

#179 Rupesh Mandhare on 05.13.11 at 7:29 am

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

#180 Dhanashree on 05.13.11 at 1:02 pm

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

#181 sree on 05.25.11 at 4:44 pm

hi ,

can u share details of that website

#182 Praveen on 05.30.11 at 11:58 am

can you please provide the bug templet

#183 NITIN on 06.07.11 at 8:36 pm

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

#184 vandana on 06.21.11 at 8:11 am

Hi,

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.

#185 Basith Shai on 07.04.11 at 2:29 am

Very informative,helpful tips

#186 Ratz on 07.21.11 at 12:24 pm

Excellent work vijay,

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

Regards..
Ratz

#187 Joel Montvelisky on 07.29.11 at 10:08 am

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,

Joel

#188 Yordys Valenzuela on 08.25.11 at 1:53 pm

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.

Yordys

#189 Samu on 09.06.11 at 8:19 am

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!!!!!!!!!!

#190 laxmi on 10.11.11 at 12:51 pm

hi
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

#191 Krish on 10.27.11 at 10:53 am

Thanks for good info

#192 mahalakshmi on 11.04.11 at 8:08 am

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

#193 mahalakshmi on 11.04.11 at 8:09 am

please provide ma a sample test case and check list

#194 HAMSAPRIYA on 11.09.11 at 11:33 am

It is a very use full report for fresher

#195 Abdul Kader on 12.29.11 at 9:10 am

This tips are really usefull to me.

#196 shalini on 01.13.12 at 8:57 am

its very useful. i learned more.

#197 thenmozhi on 01.13.12 at 9:00 am

Its very useful artical

#198 thenmozhi on 01.13.12 at 9:02 am

Its very useful to me……,

#199 shalini on 01.13.12 at 9:07 am

nice……….,

#200 S.SWETHA on 01.23.12 at 4:36 am

Hi, its very useful to me.

Thanks For your valuable information

#201 sneha on 02.02.12 at 12:00 pm

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

#202 khan on 02.20.12 at 1:54 pm

Good stuff for the beginners and intermediate testers

#203 tintin on 03.06.12 at 11:25 am

Very comedy comments… :)

#204 Santhosh Tuppad on 03.22.12 at 9:09 am

This might help you in better bug reporting. Crash Course on Bug Reporting – http://tuppad.com/blog/wp-content/uploads/2010/08/Crash-course-on-Reporting-Bugs-in-Software-Testing.pdf

— Santhosh Tuppad

#205 apurva verma on 03.30.12 at 1:50 am

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: apurvaverma1@gmail.com

#206 ankit on 05.26.12 at 6:17 am

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
id: ankit_singh027@yahoo.com

#207 sree's on 06.18.12 at 6:27 am

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

#208 Rishikesh on 06.30.12 at 5:43 pm

Very help ful thanks for sharing…!!!!

#209 sourabh bhave on 08.29.12 at 12:42 pm

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

#210 janardhan on 09.22.12 at 6:00 am

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

#211 Satish on 10.06.12 at 12:21 pm

Lot of testing learned @ ‘softwaretestinghelp.com'; thanks Vijay….

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

#212 Satish on 10.06.12 at 12:41 pm

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

#213 chirag gajjar on 10.10.12 at 8:38 am

nice report..

#214 Satish on 11.07.12 at 7:30 am

good one

#215 shankar on 11.23.12 at 11:49 am

please can you mail me the bug report

#216 http://tinyurl.com/kovamaloy09203 on 01.17.13 at 10:54 am

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

#217 http://tinyurl.com/savrjenks56781 on 01.24.13 at 8:32 am

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

#218 sarvesh on 02.21.13 at 7:07 am

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 spatel2102@gmail.com
thank you

#219 sarvesh on 02.21.13 at 9:18 am

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

Thanx
Sarvesh

#220 ranaji on 03.06.13 at 11:48 am

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

rana.adeel65@gmail.com

thanks.

#221 SAM on 03.15.13 at 11:49 am

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

#222 SAM on 03.15.13 at 11:53 am

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

“samuelprasannaraja@gmail.com”

#223 Chris Kerr on 06.10.13 at 5:04 pm

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.

#224 pritam on 07.11.13 at 5:02 am

Thanks ……for nice Experiment.

#225 Srinivas on 07.18.13 at 10:15 am

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

#226 smitha on 09.06.13 at 10:12 am

good artical

#227 Priyanka on 09.18.13 at 7:38 am

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

#228 Jayashree on 10.01.13 at 12:06 pm

Nice one thanks.

Jayashree Patil

#229 Jay on 10.03.13 at 7:46 am

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!

#230 Ashwin on 10.29.13 at 1:58 pm

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

Thanks and Regards
Ashwin

#231 Sujana on 11.10.13 at 2:08 am

This is very helpful article

#232 pradeep on 11.27.13 at 7:27 pm

hi all,

this is really nice article……………thanks for softwaretestinghelp.com

Regards,
pradeep

#233 vijayashree on 12.13.13 at 7:35 am

Vijay,

Let me know E-learning domain testing process.

#234 A Complete Guide to Usability Testing – It’s Like Trying to Read Minds! — Software Testing Help on 12.23.13 at 5:28 am

[…] tester’s job does not end with reporting the results (in case of traditional QA jobs, we report bugs and do not get involved in fixing them), it includes providing suggestions on how to make the […]