Belajar SQA Dasar - #6 Membuat Bug Report

Summary

This video provides a comprehensive guide on understanding and managing software bugs, errors, and system failures. It explains the differences between human errors, bugs, and observable system malfunctions, and introduces key concepts such as severity (safety) and priority to help determine which issues should be fixed first. The tutorial also covers common causes of bugs, including poor communication, tight deadlines, and complex software, along with strategies for prevention like clear collaboration and thorough testing. Finally, it demonstrates how to create detailed bug reports with practical examples, ensuring developers can efficiently identify, reproduce, and resolve software issues.

Takeaways

• 😀 Errors are human-made mistakes in software development and can originate from developers, designers, product teams, or clients.
• 😀 Bugs, also called defects or faults, are discrepancies between expected and actual results, often caused by errors.
• 😀 Failures occur when bugs cause the system to behave unexpectedly during testing or actual use.
• 😀 Severity (safety) measures how much a bug affects the system, ranging from low to critical.
• 😀 Priority indicates how urgently a bug must be fixed based on business impact, ranging from low to high.
• 😀 High-severity bugs can make a system unusable, while high-priority bugs may need immediate fixing even if severity is low.
• 😀 Common causes of bugs include poor communication, tight deadlines, complex software, inadequate documentation, and flawed testing processes.
• 😀 Preventing bugs involves clear communication, effective collaboration, reasonable timelines, and thorough testing.
• 😀 A proper bug report includes: bug description, ID, steps to reproduce, actual vs expected results, version, severity, priority, assignee, reporter, date, testing environment, and evidence.
• 😀 Examples illustrate the difference between severity and priority, such as login crashes (high severity & priority) versus minor UI issues (low severity, variable priority).
• 😀 Maintaining organized bug tracking with separate reports for each issue helps ensure no bugs are missed and aids developers in resolving problems efficiently.

Q & A

What is the difference between an error, a bug, and a failure in software development?

An error is a human mistake during development, a bug is a defect caused by an error that prevents the software from working as expected, and a failure is the observable malfunction of the system due to a bug or other issues like hardware incompatibility.

Who can introduce errors in the software development process?

Errors can be introduced by developers, product team members providing incomplete requirements, design teams supplying incorrect designs, and even clients providing inadequate information.

How is a 'safety bug' different from 'priority' in software testing?

Safety (or severity) measures the impact of a bug on the system, while priority measures how urgently the bug needs to be fixed based on business impact or project deadlines.

What are the four levels of bug severity?

The four levels are: Low (minor effect), Minor (affects parts but system still works), Major (disrupts important functions, fix immediately), and Critical (system unusable, urgent fix required).

What are the three levels of bug priority?

Low (can be fixed later), Medium (fix during normal workflow), and High (must be fixed immediately due to major business impact).

Can you give an example of a bug with high priority but low severity?

Yes, for example, a checkout button misaligned on Chrome may not affect system function but negatively impacts user experience and sales, so it has high priority but low severity.

What are some common causes of bugs in software?

Common causes include poor team communication, tight deadlines, complex software with many modules, poorly documented code changes, and inadequate or improper testing processes.

What steps can be taken to prevent bugs?

Prevention includes maintaining good communication, fostering collaboration, avoiding rushed work, setting realistic deadlines, and conducting thorough, systematic testing.

What are the key components of a bug report?

A bug report should include: description, bug ID, steps to reproduce, actual result, expected result, version, severity, priority, assigned developer, reporter, date found, testing environment, and evidence such as screenshots.

In the bug reporting example, what was the issue with the search feature?

The search feature allowed numbers in the input field, which violated the specification that only letters are allowed, and it did not display the expected warning message.

Why is it important to include evidence in a bug report?

Evidence like screenshots or recordings helps developers understand the issue clearly, verify if the bug is new or recurring, and ensures accurate tracking and resolution.

How should bugs be prioritized when multiple issues are found?

Bugs should be prioritized based on a combination of severity and business impact, starting with high priority and high severity issues, followed by high priority but low severity, then low priority and severity issues.