Hi, I’d like to give you some worthy recommendations regarding your bug reporting. I don’t doubt that you’ll greatly benefit from those tips listed here below.
From my point of view you should widely use screenshots in your bug reporting. Of course you know that one picture is worth more than one hundred words. Each time you come across an error, you’d better capture some screenshots of the particular moment. It’s clear that if an error is clearly seen on the screenshot it will help the developer to have a perfect understanding of the problem. On this stage any developer does his best to understand the problem and only on this condition it’s possible to fix it. Your screenshots should be attached to the bug report as evidence. Thus you’ll be able to explain any bug with more clarity to the developer.
As you know from time to time a software tester needs to make sure that bugs mentioned in his report are real bugs which should be subject to fixation, otherwise they may affect the performance of the corresponding application. During this course, a software-testing engineer should be ready to face some problematic situations with the programmers.
Very often developers say that a particular bug is impossible to reproduce. The best way to report the bug is to show it to the developer. You can do it by simply asking the developer to have a brief look at the scenario. Certainly this scenario is already available on your computer system. So you should load the corresponding application and provide the developer with a highly informative live demonstration of the problem. This will provide the developer with an actual feel of this particular situation. The developer will know how this software reacts to all the inputs provided. In my opinion you’d better stay away from reporting of non-reproducible bugs. There’s no need to report maximum number of bugs.
As you know software testers often come across some funny circumstances with certain application that have rather an inconsistent pattern of failure. I should say that such situations are likely to arise when a tester experienced pressure of deadlines and the application when the test fails. Certainly the tester faces some embarrassing moments when demonstrating it to the developer. As follows from this a professional tester should be very patient. He should be concerned with creating a reliable defense mechanism to preserve the test data as well as screenshots to justify all his statements.
If a tester provides the developer with a big list of actions and inputs etc but anyway the program goes on failing to show anything wrong when being run on the system of the developer. So I just want to say that it means that the tester hasn’t provided the developer with sufficient information. I hope you’ll never disappoint your developers.
Today our world is the world of modern technologies. These days the more your activity is automated, the better, in particular when it refers to Reporting Services. Reporting is a very helpful thing. So if you want to automate your reporting activities, you might consider using SSRS solution. Having reporting automated will lead to eliminating repetitive tasks and saving time and money. Look through this SQL Server Reporting Services site to find out more details.
And keep in mind that we live in the world of high online technologies. It would be intelligent to avail oneself of the online network to look for anything at the best prices available on the market. Search engines, social networks, blogs and forums – all this will assist you to solve many issues.
convert this post to pdf.