JuniorLearnsToCode

Reporting bugs is an unavoidable part of SDLC and it is an integral part of any tester's job. It's usually done using bug-tracking software such as Jira, Rally, Bugzilla, Mantis, Azure DevOps, etc. In this post, I will share a few general (common-sense) tips on writing a clear and useful bug report. Well-written and understandable bug reports save time and can be a significant contribution to the quality of the product - especially if we prioritize those bugs which negatively impact the user experience and block the core functionalities of the application under test. So let's see what we can do to make our bug reports better.  Root Cause Analysis  Before reporting we need to make sure our defect is valid, we should check for human errors such as an outdated (no longer support) app version, configuration settings, user or systems settings - checking the logs can help us a lot here. Root cause analysis can be added in the form of testing notes to the defect ticket. If the tes...

We often hear that everything is a matter of perspective and in light of that notion I have to admit that there was a time in my career when I wanted to give up on testing. Due to having seen testing in a wrong (and rather shallow) light, I pondered hard about leaving it for good for a career in web development. So, let us get into the meat of things. Now, when I talk to people I offer hear them describing me as someone who enjoys testing and is genuinely passionate about software quality. So how was it that I found myself in a situation where I wanted to quit being a tester if I love it so much? It was many years ago, and while I can't disclose exact details, I can talk about it in general terms. This blog post is in part inspired by my personal experience and also by observations I made while talking to lot of testers trough the time - and most of them relatively similar experiences to share, from some point at their career. It is my hope that by discussing things such as this on...