Bug Advocacy · A BBST Workbook by Kaner, Cem -- Read -- Imperial Library of Trantor

Index

Titlepage Copyright About the Authors Table of Contents Preface

About this Workbook Who This Book Is For About This Book’s Structure About BBST About The Design Of The Bug Advocacy Course

LESSON 1: Basic Concepts

Lesson Introduction Readings Orientation: Quality Definitions Slides And Notes Application: Joining An Open Source Project

1. Download OpenOffice 2. Sign On To The OOo Team 3. Review The OOo Project Documentation 4. Familiarize Yourself With The Bug Database

Authors’ Reflection On Lesson 1

The Orientation Activities The Meaning Of “Quality Is Value To Some Person” Where Students Have Had Trouble

An Exam Question Dealing With Objective Versus Subjective From A Subjective Viewpoint From An Objective Viewpoint Grading Notes For This Exam Question

Lesson 2: Effective Advocacy: Making People Want To Fix The Bug

Lesson Introduction Readings Orientation: Your Experience With Bug Reporting Orientation: Tell Us What Bug You Are Working On Slides And Notes Application: Evaluating Bug Reports: Phase 1

1. Guidance For The Assignment: Think In Terms Of RIMGEN

Distinguishing Between Coding Errors And Design Errors

2. How To Do Follow-Up Testing

Follow-Up Testing To Maximize A Failure

1. Vary Your Behavior 2. Vary The Options And Settings Of The Program 64 3. Vary Data That You Load Into The Program (The Data Environment) Case 1: A Good Example Of Varying Data Case 2: A Bad Example Of Varying Data Case 3: A Confusing Example Of Varying Data 4. Vary The Software And Hardware Environment 65 How Much Of This Should You Do?

Follow-Up Testing To Generalize A Failure

1. Uncorner Your Corner Cases 2. Look For Configuration Dependence 3. Check Whether Many Different Paths Will Lead To The Same Failure 4. Check Whether The Bug Is New To This Version 5. Check Whether Bugs Like This One Already Appear In The Bug Database 6. Check Whether Bugs Of This Kind Appear In Other Programs

Authors’ Reflection On Lesson 2

Making The Underlying Theme More Explicit Different Analyses For Coding Errors Versus Design Errors Improving The Presentation Of Follow-Up Testing

Lesson 3: Writing Clear Bug Reports

Lesson Introduction Readings

Style And Content Of The Bug Report Severity, Priority And Related Fields Disfavored Fields The Problem of Duplicates Qualitative Measurement

Orientation: Writing An Attention-Grabbing Bug Summary Slides And Notes Application: Evaluating Bug Reports About That Bug Evaluation Guide

Real-Life Performance Evaluations Qualitative Measurement

Authors’ Reflection On Lesson 3

Lesson 4: Irreproducible Bugs

Lesson Introduction Readings Slides And Notes Authors’ Reflection On Lesson 4

Lesson 5: Bugs That Could Be Dismissed As Unreasonable Or Unrealistic

Lesson Introduction Readings

Writing A More Effective Design Report Should You Write Design Reports?

Slides And Notes Application: Evaluating Bug Reports, Phase 2 Authors’ Reflection On Lesson 5

Some Personal History

Design Issues Are Often Serious Organizational Dynamics

Persuasive Communication In An Organization: Three Key Questions

1. Who Will Listen To (Or Read And Act Upon) Your Report? 2. Who Are They Likely To Listen To? 3. What Arguments Are They Willing To Hear?

Some Quibbles With Terminology

Objections To The Concept Of Bug Advocacy

Lesson 6: Credibility and Influence

Lesson Introduction Readings Slides And Notes Supplementary Thoughts On Decision Theory

The Core Concept

Case 1 (Same Percentage Fixed As Before): 168 Case 2 (The 1000 Additional Bugs Were Mainly Less Significant): Case 3 (Only 1000 Bugs Were Reported, But They Were All Good Ones):

Improving The Group’s Accuracy Versus Changing Their Bias

Case 4 (Report Only The Most Important Bugs) Case 2 And Case 4 Are Both Full Of Mistakes Changing The Decision Criterion Changes Subjective Experience Applying This Analysis Beyond The Tester What The More Formal Model Looks Like (OPTIONAL Reading)

The Power And Operating Characteristic Of A Test Generating An Operating Characteristic From Decisions Adding Some Psychological Theory

Application: Evaluating Bug Reports: Phase 3 Application: Applying The Decision-Making Model Authors’ Reflection On Lesson 6

Assignment: Replicate And Edit Bugs

This Appendix Contains The Assignment Instructions The Assignment Workflow The Assignment’s Details

Phase 1

Search for an unconfirmed bug in the OpenOffice database

Phase 2 Phase 3 Flowchart For Phase 1A Flowchart For Phase 1B

How To Evaluate A Bug Report

Evaluation: First Impressions 186 Evaluation: Replicate The Report Evaluation: Follow-Up Tests Evaluation: Tester’s Speculation Or Evaluation

Feedback on Activities

Introduction: The Answers At The Back Of The Book Orientation: Writing An Attention-Grabbing Bug Summary

Our Notes On The Summary

Problem 1: Vague, Vague, Vague Problem 2: Overemphasis Of Minor Details FAILS, WHEN PROTOCOL

Our Notes On The Follow-up Tests

Application: Apply The Decision-Making Model

Advice for Answering Essay Exams

Overview Answering Essay Exams Well

Preparing For The Exam Starting The Exam

Skim The Questions Develop A Budget For Your Time Choose The Order Of Your Answers

Answering The Questions

Look For The Call Of The Question Be Aware Of The Meanings Of The Question’s Words Outline Your Answer Structure Your Answer According To The Outline. Emphasize The Structure

Ground Rules A Closer Look At Some Common Problems

Structure Shotgun Answers Weak Group Preparation Weak Answers Propagate Through The Group Failure To Consult Required Readings

Resources

References Index

← Prev
Back
Next →

← Prev
Back
Next →