Software QA and Bug Reporting

Name: Software QA and Bug Reporting
Author: Andrew Levin

Communicate issues found in your software with others

Preview the first lesson free — get full access to all 3 lessons.

Course: On-Demand

Hello everyone. Welcome to software QA and bug reporting. In this module we're gonna talk about all kinds of things dealing with bug reports. What exactly is a bug report? Why do you need a bug report? What's the best way to make a bug report? In this lesson we're gonna talk about the basics of a bug report. What exactly is it? So in previous lessons we had testing, we had different types of testing. Let's say during that testing a bug appeared. You use a bug report to document it. If you don't use a bug report to document it and you simply try to fix it, what if that didn't fix it? What if it causes an error someplace else? You have no way to track. So we're gonna start with the basics in this lesson. What is a bug report? It's a detailed description about the bugs. When you come across a bug, be it a syntax, meaning you type the code incorrectly, or a logic error. You need to document it. You gotta give a description about what happened, when it happened, who found it? What unit were they in when this happened? Does it affect anywhere else? But probably the most important part of a bug report is was it repeatable? Meaning if I type in A, B, C, and the letter Q, I get a bug. Every time I type a, B, C and the letter Q I get a bug. That's repeatable. But if you can't repeat it most likely you haven't fixed it. 99% of the time if you get a bug, there's a problem in the software and you need to find out what happened. Repeating or repeatability is the most important thing to be able to do. But you do have to document everything. Now you might think while documenting, that's gonna be a lot of time, but it's a lot of time if you don't document it, going back trying to fix it. So, luckily we have a lot of pre-made bug reports out there. You can get these, they're free to use, people put them on the internet. Let's look at a couple and you'll see the commonalities. But a great site as it was on that PowerPoint leads you here, Marker.io. Here's a bug report template in Excel. Here, we'll do one in Word. Let's bring it all the way down here, here. This is a nice setup. This is the Excel one, here's Word. So you can download it and it'll open up in Word for you. And if you look, the categories no matter how you open it up are all gonna be the same. A key field, you have to have a bug ID, name, reporter, et cetera, et cetera. Here's the bug overview. Screenshots are excellent. A picture's worth a thousand words. What was, what the environment was, any details, the bug tracking, any notes. You wanna be flexible but these are a great way to start. So like I said this is a basic overview of bug reporting and I have this right here to lead you to the templates when you need them. So thanks for coming and I'll see you in the next lesson.

Beginner Provider : Andrew Levin 3 Lessons · 12m in Arabic, German, English, Spanish, French, Portuguese, Urdu, Chinese

Course Description

In this chapter you will learn about Bug Reports. You will how to construct a good Bug Report by seeing which fields to include and suggested data to fill in the fields with descriptive and appropriate data. You will also see what should and should not go into a proper Bug Report.

What You'll Learn

Define what a Bug Report is and why it is needed during testing
Identify the individual components and elements of a good Bug Report
Construct an effective Bug Report by selecting which fields to include
Fill report fields with descriptive and appropriate data
Determine what should and should not go into a proper Bug Report

Key Takeaways

A Bug Report is a structured document used during software testing to record defects.
Bug Reports are necessary to communicate issues found during testing.
A good Bug Report is built from specific fields filled with descriptive and appropriate data.
Knowing what to exclude is as important as knowing what to include in a proper Bug Report.

Frequently Asked Questions

What does this course cover?

This chapter covers Bug Reports: what a Bug Report is, why it is necessary during testing, and the elements of a good Bug Report, including which fields to include and what should and should not go into a proper report.

What will I learn about constructing a Bug Report?

You will learn how to construct a good Bug Report by seeing which fields to include and suggested data to fill in those fields with descriptive and appropriate data.

What skills does this course relate to?

The course relates to Problem Reporting, Bug Tracking and Management, Code Review, Software Coding, Software Documentation, and Software Technical Review.

What lessons are included?

The lessons are: What a Bug Report is, Why a Bug Report is Necessary, and Elements of a Good Bug Report.