Hot answers tagged

6

There will always be bugs that get past a tester and land in production. I have even had bugs that where in my face, we researched it, thought it was a fluke, because we couldn't reproduce it and then released the issue into production. The best thing you can do is learn from it and prevent the same in the future. I write an automated test-case for each ...


2

You wish to check your code in to keep it save. The testers test everything they can see, maybe because it is not clear what is not finished, or maybe just for another reason. There are a few actions you can take to stop this problem. You could use Feature branches You only merge the code into “main” when it is finished Other developers can see what ...


2

First and foremost, analyse how the bug got past you. Find a way of preventing this, and things like it from happening ever again. Second and maybe even more important, talk. Talk with everyone involved with getting new functionality out. As soon as requirements materialize, get your test approach on paper and scrutinize it AS A TEAM. That a harmful bug got ...


1

As a tester, I love exploring partially developed code, and giving early feedback to the developer. The key thing, as others have mentioned, is strong communication between developer and tester. I need to know what areas are likely to still be incomplete, so I don't waste time trying to isolate an issue. The developer needs to be prepared to outline what's ...


1

If you was under the threat to lose your job as a result of letting a single bug to slip to PROD, you should consider looking for a job in saner company. It is just a matter of time when another bug will slip to PROD. Quality is a team sport. Bugs will always slip, and pointing fingers and assigning blame does NOT improve quality. Firing you for a bug is ...


1

Is it normal? Yes and no. I would say that first and foremost if you are in an AGILE environment, the product owner or someone else should be scrubbing duplicate defect reports before committing them. Also, testing tasks should be presenting to QA once a feature is working, not typically before. That just wastes precious QA time and makes the backlog messy. ...



Only top voted, non community-wiki answers of a minimum length are eligible