Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Should programmers itemize testing for projects? [closed]
Closed 10 years ago.
Should programmers itemize testing for projects? [closed]
Closed 10 years ago.
Should programmers itemize testing for projects? [closed]
Closed 10 years ago.
Fixing bugs may lead to delayed feedback [closed]
Closed 10 years ago.
Fixing bugs may lead to delayed feedback [closed]
Closed 10 years ago.
Fixing bugs may lead to delayed feedback [closed]
Closed 10 years ago.
Multiple documentation issues in a single bug
It is clearly a bad practice to incorporate several issues in a single bug. It is not convenient, hard to maintain, difficult to keep track of what is done and what is not, etc.
Multiple documentation issues in a single bug
It is clearly a bad practice to incorporate several issues in a single bug. It is not convenient, hard to maintain, difficult to keep track of what is done and what is not, etc.