178
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 ...
44
votes
Accepted
Asking a developer to be explicit about how a bug was fixed
I would operate under the assumption that your developers are documenting this somewhere, since I would also assume that they are good developers who care about good development practices. As a ...
34
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 ...
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 ...
29
votes
How to respond to requests to retest, in hope that the bug is gone?
As a developer, not a QAist, I have a responsibility to provide software that meets the specs, with as few errors as possible. From my perspective, QA has the responsibility to inform me of any errors ...
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 ...
26
votes
Accepted
Who is responsible for pinpointing bugs?
If request sounds reasonable (which includes taking into account my other priorities), I would spend some more time researching.
If not reasonable, I will respond "sorry this is the best I can", and ...
23
votes
How can developers improve relations with testers?
Good and Interesting question.
Here are some to make the tester's job easier:
Developers should perform basic testing before giving the product to the tester.
Include QA from the beginning of the ...
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 ...
21
votes
User reports a bug, send it to QA first or Programmer first?
It depends
Each company has its own process for handling customer-reported defects. The one I'm most familiar with is more or less as follows:
Customer support person attempts to reproduce defect and ...
20
votes
How to respond to requests to retest, in hope that the bug is gone?
I see several possible problems here:
There are reported bugs that the test team can apparently reproduce but the development team has trouble finding/fixing. This suggests that there is insufficient ...
19
votes
How to convince project managers that onboarding a tester early is important?
In this situation - unfortunately - your best option is the slow and painful method. I've used it as a general tester, and for test automation.
The way I approach this is to use these techniques:
...
18
votes
User reports a bug, send it to QA first or Programmer first?
It depends on your policy if you have one. It could go either way.
It could also be that it goes to the PO and they should approve it before continuing with the fix or putting it in the backlog.
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 ...
14
votes
How can developers improve relations with testers?
Treat them as equals.
I have seen a lot of developers thinking they are more or better then testers in their companies and also treat them that way. Developers and testers have a similar goal: Making ...
14
votes
Who is responsible for pinpointing bugs?
It depends.
As Joe Strazzere explained, it is a matter of discussion between devs and testers. The question is what factors to consider in such a discussion. I think Danny R. Faught explained that ...
14
votes
Asking a developer to be explicit about how a bug was fixed
Request a meeting between upper management of QA and DEV and explain the goals of what you are asking. I think the description you provided in the question is a good start at explaining the why of the ...
13
votes
How can developers improve relations with testers?
I've worked in both roles for a while and my recommendation is:
Pair (before coding when possible) on test plans
See QA as an asset that is protecting you and customers from the mistakes we all make
...
13
votes
How can developers improve relations with testers?
Just a few quick ones off the top of my head:
Run the code they've completed at least once on their machine before marking it as 'Done'.
Consult with QA on their intended route to implement a feature ...
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 ...
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 ...
10
votes
Accepted
Signal to noise ratio during early testing
Greater communication between dev and qa so that qa already knows about wip issues.
Communicate first in person where there is disagreement, then document the agreement.
Clear definition on what ...
10
votes
User reports a bug, send it to QA first or Programmer first?
It depends on the company to company and it's organizational work culture.
In my current and previous companies,
When a end user reports a bug first it goes/assigned it the QA team.
Then the QA team ...
9
votes
Who is responsible for pinpointing bugs?
Many companies I've worked for shared a policy...
...and that policy is:
Testers are free to consult with developers while attempting to characterize, isolate or reproduce anomalous behavior.
Once a ...
9
votes
Asking a developer to be explicit about how a bug was fixed
Most other answers suggest that requirement to be better in testing is understanding the code - but that requires skills what most QA testers do not possess. Deep understanding the code is not ...
9
votes
User reports a bug, send it to QA first or Programmer first?
First of all users should report using a reporting system, they should not be aware where does it go.
From there it depends on the size of your company, the product and how mature it is, the SLA you ...
8
votes
Accepted
Why testing is not a stand alone activity
Testing is not a standalone activity because:
resolving bugs means talking with product and development to make sure that the bugs are well understood and that the path to correct them makes sense ...
7
votes
How can developers improve relations with testers?
This is a simple point, but very effective:
Be a developer who says "thanks" or "good catch!" or something positive whenever a tester finds a defect.
It's the daily currency of the respectful ...
7
votes
Should a tester feel bad about finding too many defects/bugs in the product?
No, of-course not, not even when you find defects in an application that you already tested and did not change. Think about it this way, you keep growing and learning. So you will find better ways to ...
7
votes
Who is responsible for pinpointing bugs?
But, what are the general ways to avoid having or deal with such
conflicts keeping the relationship between the teams healthy and
productive?
Both QA management and Development management must ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
programmer-relations × 39development-process × 10
team × 9
qa-developer × 7
automated-testing × 5
manual-testing × 4
test-management × 4
bug-report × 4
management × 3
unit-tests × 2
quality-assurance × 2
interview × 2
qa-role × 2
team-management × 2
requirements-engineering × 2
culture × 2
tester × 2
jmeter × 1
python × 1
test-design × 1
load-testing × 1
api-testing × 1
testcase × 1
performance-testing × 1
agile-testing × 1