How does a tester decide how much debugging/investigation to do before handing an issue over to development?
A common question from the testers I mentor is "When do I stop investigating on an issue, log a defect with everything I've found/determined so far, and hand it over to dev?" I have yet to come up ...
As a developer my knowledge of best QA practices, etc., are limited to know just enough to get me by writing unit tests, etc. From a tester's point of view, what testing procedures should the ...
In my team, there are a number of experienced QA people. I work mostly on developing tools to make the QA process easier for these guys, such as developing test automation. The uptake has been slow, ...
In my firm, we don't have testers, exactly. We have analysts who translate business requirements into specifications. (Think the guy from Office Space, except these guys actually provide some value. ...
Perhaps programmers have their own unit tests, perhaps as the result of doing Test-Driven Development. They run these tests very often; perhaps every few minutes, but at least a few times each day. ...
Suppose you're working with bright programmer, but every time you test the code you find a serious, obvious bugs. Things the programmer could have noticed if they did their own testing before checking ...