Black box software testing: A course by Cem Kaner & James Bach
Bug Avocacy 2
- Video lecture (coming this summer)
- Lecture slides: (PPT) Effective writing: Dealing with objections
- Lecture slides: (PPT) Reviewing & editing bug reports
- Lecture slides: (PPT) The mission of the tracking system & your credibility as a reporter
- Multiple choice review questions
- Essay test questions: Objections
- Essay test questions: Editing
- Essay test questions: Mission & Credibility
- Assignment: See Bug Advocacy 1
- Assigned reading: Kaner, Bach & Pettichord: Lessons Learned in Software Testing, Chapter 4, Bug Advocacy.
This continues the material on bug advocacy. Several factors influence the programmer's decision to (not) fix a bug. Bugs are unlikely to be fixed if they are hard to reproduce, hard to understand, or that look trivial or highly unlikely--or were reported by someone who has no credibility or goodwill in the development group. We look at ways to edit bug reports to eliminate common problems and at ways testers sabotage their own credibility.
We are setting up a mailing list for announcements about this course and, perhaps, a tightly focused and moderated discussion of how to teach it or self-study with it. (This won't be a general, high-traffic, intro-to-testing discussion.) If you're interested in the course, please sign up by sending us an email. We will NOT share your email address with third parties or send commercial advertising to you.
We are publishing this course under a Creative Commons license that allows you to freely reuse and distribute the materials and to modify the slides and associated printable materials (but not the videos). We would be appreciate a few mirror sites, to reduce the growing burden on our servers. If you can help in this way, or any other way, please send a note to Cem Kaner.
