Browsed by
Tag: bug report

8 Essential Bug Reporting Skills Every QA Agent Should Have

8 Essential Bug Reporting Skills Every QA Agent Should Have

Being a QA agent is a demanding job. It requires you to be diligent in your work to ensure everything is up to standards. When you’re a QA agent you’ll come across the need to complete manual testing when carrying out a bug report and it could be, that you don’t yet have DebugMe in your toolset. Bug reporting as a QA agent is one of the essential skills that you should have. For those who want to become a QA agent, this expert guide will give you the run down on the essential bug reporting skills that every QA agent should have. Let’s take a look.

bug reporting skills qa agent

Read More Read More

Manual Testing: 12 Practical Tips

Manual Testing: 12 Practical Tips

Manual testing done great and being the manual tester of your customer’s dreams is no easy task. There are many things to keep in mind to produce the best user acceptance testing results for your customers. A very important concept to remember for testing is quality over quantity. If something isn’t tested thoroughly, you AND your customer’s credibility both take a hit. Why not strive to be on the other end of that spectrum? Here are 12 manual testing tips to be a cream-of-the-crop manual tester by making sure you do everything your customers ask, and then some.

manual testing

Are you a front-end developer or a web designer? This tool will save you hours and make your life easier

Read More Read More

Bug Report: The Good, the Bad and the Ugly

Bug Report: The Good, the Bad and the Ugly

Bug reporting may not be the most fun activity in the world, but doing it the right way by the right person is very helpful and efficient when it comes to optimizing projects. There have been some hideous attempts at bug reporting. Some, from sheer laziness. Others, from forgetfulness. And even some, from over-creativity because there is a multitude of ways you can produce a bad bug report.

bad bug report

What constitutes a bad bug report?

A bad bug report would be one that isn’t filed in the right place. It may have useful, clear, and well thought out content but filing it in the wrong place isn’t the best way to communicate with a developer. An example of this would be sending a tweet or an email. Tweets can turn into long chats about finer details. Emails are bad because bug reports aren’t the only things popping up in them. It’s overall an unreliable and decentralized way to send a bug report.

Are you a front-end developer or a web designer? This tool will save you hours and make your life easier

Read More Read More

Become Your Developers Best Friend by Sending Them A Perfect Bug Report

Become Your Developers Best Friend by Sending Them A Perfect Bug Report

Developers understand that their work won’t be perfect on the first try. It may initially compile, but there will always be bugs. As a user or a tester it is important that your bug reports are clear, concise, and informative. A perfect bug report is able to effectively tell the developer where, what, and how, so they can address it in a timely manner.

perfect bug reports

Here are some key points to writing the perfect bug report

1. Descriptive Title

This is the first thing seen by the developer. You want this to put the entire problem into context. Something like “The calendar doesn’t respond to home page navigation.”

Are you a front-end developer or a web designer? This tool will save you hours and make your life easier

2. Concise Description

You want them to know exactly what happens and be able to walk your soon-to-be best friend through the steps to re-create the problem. E.g. – “When clicking “calendar” on main menu of the “about” page, the calendar pops up. And when you navigate back to the “home page” with the top left icon, the calendar stays on the screen after you navigate, obstructing the view of the “home” page”. You want this to be under 140 characters to put the size and briefness into perspective.

3. What you expected to happen from the action

E.g. – “When I click on the home page icon while the calendar is up I expect the calendar to close as I navigate to the home page”

4. What actually happened

E.g. – “The calendar stays up even after the site navigates to the home page and it obstructs the page”

5. What version of the software and what system are you using

Maybe they could be working on a new version that fixed that bug or they didn’t write it to be completely compatible with your system. Checking the smaller details like these are essential for saving time thinking about what could be a small issue.

Read More Read More

Bug Reporting and Handling a Bug Report the DebugMe Way

Bug Reporting and Handling a Bug Report the DebugMe Way

The bug reporting process is usually long, painful and unpleasant for everyone involved, where it’s a lot of times difficult to even define and find the exact problem. Businessmen and simple end users not always speaking the same language as the developers and because of that people are sending more angrier and angrier emails back and forth… the whole thing can be just a terrible experience. Wouldn’t it be great if a bug report would be easy to create and clear to look at while having every piece of relevant information? We have good news for you.

Bug Reporting 101

What is a bug report? Well, a good and easily understandable bug report must contain all the information the developers need in order to identify and fix the problem or problems the report is about. If you want to achieve that in an efficient and headache-free way the bug reporting must be as simple and straightforward as it’s possible. Essentially you have to create a user-friendly bug report.

Gather All the Information You Need, but Only What You REALLY Need

Just search for “bug report” in Google’s image search and after a few seconds of looking at the results close the tab as fast as you can. For those who don’t want to participate in this experiment you’ll see pictures similar to this:

bug reporting

No one wants to deal with a bug report like this. No one wants to deal with “endless chain of emails and screenshots” type of bug reports or bug reports you only heard about over the phone, etc. DebugMe offers a better way: a bug report with all the useful information by one click and a work process in a beautiful kanban system with everything you need to know, visualized. It does sound appealing, doesn’t it?

Read More Read More