This lesson describes possible ways how to decide it’s a bug and how to explain it to the team.
In this video you will learn about:
Testing using an example of OpenOffice and WordPad's font size display. It emphasizes the importance of comparing results to expectations and reference programs, highlighting inconsistencies as potential bugs. The concept of Oracle heuristics is introduced, acknowledging human judgment in evaluating test results. The example demonstrates the need for thorough testing, considering various fonts, characters, and interactions. The discussion explores the credibility problem in reporting bugs and the significance of consistency heuristics in guiding test design. The video concludes with the idea that understanding a product's purpose is crucial for effective testing and bug reporting.
Discussed terminology:
No specification is complete
How serious is the bug
How to explain to others that it’s a bug
Where to look for information and expectations about software