177
votes
Should a tester feel bad about finding too many defects/bugs in the product?
There is only one situation where a tester should feel guilty about finding too many bugs in a product, and that's if all the bugs that are found are symptoms of the same bug.
I was working on a game ...
- 1,631
82
votes
How should a Software Tester deal with missed Defects/bugs in Production?
Company pays me to test good and not be careless.
You are asking this question here - you are not careless, you care about the job you do and the things you can improve on.
Don't take it personally ...
- 11.4k
56
votes
Should Testers first discuss a bug with the developers before writing a bug report?
As a developer with 15+ years experience, I'd say: please report the bug. I'd much rather have a ticket in the tracking system than a vague memory of a hallway conversation, or an interruption of what ...
- 631
37
votes
How should a Software Tester deal with missed Defects/bugs in Production?
Please do not resign.
As alecxe has said in his post, Perfect Software is a myth.
I would like to add, the difference between a tester and a developer is: It is very difficult to see how much a ...
- 9,740
36
votes
Accepted
What if the software is so buggy it can't really be tested at all?
Continue testing in this situation would be counter-productive and may lead to a "deadlock" - when the reported issues would depend on each other recursively.
make sure the management is aware of the ...
- 11.4k
33
votes
Should a tester feel bad about finding too many defects/bugs in the product?
Your job is to find bugs that could negatively impact those using the program, and in the health arena, these bugs could also potentially impact patients as well.
If you find flaws and true bugs that ...
- 431
31
votes
Should a tester feel bad about finding too many defects/bugs in the product?
I'm going to address what I feel is the elephant in the room here because none of the other answers has really mentioned it yet. Note that this answer is based on the wording of the question. I may be ...
- 475
30
votes
Accepted
What would be the strategy when too many bugs are found in the final round of testing?
It depends
I've been in this situation more times than I care to remember, and the general process I use works this way:
Triage all findings - At this stage I would be working to triage all bug ...
- 30.8k
26
votes
Should a tester feel bad about finding too many defects/bugs in the product?
Is there someone responsible for deciding what bugs should be fixed? If so, how do they feel about it?
Is there a specification that the software is not meeting?
You need to log everything that is ...
- 764
26
votes
What should a Software Tester do to become more valuable and helpful for the Development Team?
It is very admirable for you to consider a tester's role from this perspective.
The hard cold fact:
No one is happy when there is a bug found in their code. Imagine yourself as a developer, you ...
- 9,740
23
votes
Should a tester feel bad about finding too many defects/bugs in the product?
Obviously you shouldn't feel bad for doing your job.
As for feeling good and being sure you really are doing your job well however there are a number of other things you can consider. Your feelings ...
- 24.5k
22
votes
What is the Real Business Value of Software Testing in an IT Project?
I work as a Manual tester on a big project. My project follows Agile methodology. I test a Web-based application. I sometimes ask my self , that am i giving any value to the stakeholders?
So, the ...
- 3,232
22
votes
How should a Software Tester deal with missed Defects/bugs in Production?
As the other answers have said, do not blame yourself. Nobody can test any piece of software completely, any more than anyone can write completely bug-free software. It's too complex.
I'm going to ...
- 30.8k
17
votes
Accepted
How to handle client if you found a high severity defect on the release date?
This is a simple, if uncomfortable, situation to be in. Unfortunately, it does happen from time to time and you need to be ready for it.
The fact that the defect has been found close to the deadline ...
- 608
17
votes
Should a tester feel bad about finding too many defects/bugs in the product?
Simple answer 'NO!'
Complex answer 'No, provided you are doing the following...:'
You are reporting relevant bugs (i.e. deviation from requirements) or things which can be shown to impact functional ...
- 423
17
votes
What should a Software Tester do to become more valuable and helpful for the Development Team?
For testers to become more valuable and helpful for the development team...
Focus on helping developers earlier in the process
Focus on adding value much earlier in the process. Focus on working with ...
- 24.5k
16
votes
Should Testers first discuss a bug with the developers before writing a bug report?
In my own experience, I've found that this really depends on the culture of the team or company that you're working with.
On a team with good communication skills, and where everyone works together ...
- 6,066
15
votes
Is it mandatory to include "Actual results" section in a Defect/Bug Report?
What does your company management and the dev team say?
Do they require that piece of information in the Bug Report?
As a tester when you are reporting bugs you need to make sure you provide all the ...
- 7,260
15
votes
What is the difference between Major and Minor Bug?
Major has more impact on how users can or cannot use the application than minor.
There is no industry standard what these terms mean. If it is necessary, you need to discuss the meaning with your ...
- 32.2k
14
votes
Accepted
How bug prioritization works in agile projects vs non agile
A generic answer is: It's contextual; the team and stakeholders (which is who understand better the context) should work towards finding a good way - and periodically analysis its efficacy and improve ...
- 10k
12
votes
Should Testers first discuss a bug with the developers before writing a bug report?
We prefer to talk to developers first. Then, we together decide if detected error is a result of some quirk in processing and not even worth of bug, or, if it is worth a bug, we negotiate who will ...
12
votes
Should Testers first discuss a bug with the developers before writing a bug report?
Do not discuss defects immediately with developers. Mainly because context switching is bad for their focus and could take up to 5-30 minutes to recover from.
How to communicate a defect depends in ...
- 32.2k
12
votes
Should Testers first discuss a bug with the developers before writing a bug report?
I think, it is always good to discuss things in person. You are lucky you have that things going on at your work place. In many companies all communication happens only via a system and that at times ...
- 121
12
votes
How to handle client if you found a high severity defect on the release date?
Deciding to release with severe bug (and escalate next release with a fix) or postpone release is business decision. It can be done only by someone who understands how customer works.
Maybe it is not ...
12
votes
Should a tester feel bad about finding too many defects/bugs in the product?
You should not stop finding bugs.
You may want to adjust how you report them. As RomSteady pointed out, creating a ticket for each failed link when all have the same root cause is not efficient, and ...
- 482
12
votes
What if the software is so buggy it can't really be tested at all?
Ideally, suspend the testing. And it's time to refer the Test Plan document.
This is the time when one should look at the Testing suspension and resumption criteria section in the Test Plan document.
...
- 1,712
11
votes
Should a tester feel bad about finding too many defects/bugs in the product?
If this is a medical application you are talking about it is serious stuff. What if the bugs affected real users? Developers would be much less happy if they put in life threat someone or if ...
- 211
11
votes
What should a Software Tester do to become more valuable and helpful for the Development Team?
From the perspective of a developer,
I am a freelance developer, and as such I work with many different QA setups. From one guy testing everything to full teams of people checking down other teams of ...
- 211
11
votes
Accepted
Is it valuable to measure bug count per hour of dev time?
No
It absolutely is not valuable to measure bug count per hour of dev time. It is especially bad to measure bug count per hour for individual devs.
Devs on more complex or difficult code will ...
- 30.8k
10
votes
How should a Software Tester deal with missed Defects/bugs in Production?
You are too hard on yourself.
Let me give you some insight on testing: you might wonder why testers even exist: if everyone would do a good job, testers would not be necessary.
Is this true? No, it ...
- 253
Only top scored, non community-wiki answers of a minimum length are eligible