In this first lecture, Cem Kaner presents an overview of the online BBST courses and introduces some definitions commonly used in the testing field.

In this second lecture, Cem Kaner talks about why testers test, what they are trying to learn, and how they can organize their work to achieve their mission.

Kaner’s topic for this lecture is how oracles are used as heuristics to help testers determine whether or not software passes the tests that are run.

Kaner presents information about basic data handling and storage to help testers think about the multi-dimensional problem of test coverage in more sophisticated ways.

In this fifth lecture, Kaner explores the complexity of determining when testing is finished and how the goal of complete testing is unattainable.

In this lesson, Cem Kaner addresses the challenges of measurement in software testing and introduces you to software metrics.

In this 35-minute lecture, Kaner explores a range of definitions for basic concepts including “quality” and “bug.” He also presents the multi-dimensional view of quality used throughout the BBST courses.

Lecture 2 focuses on how to develop bug reports that clearly communicate bugs in their best and most honest light so that decision-makers can operate with the best possible information.

In this lecture, Cem Kaner introduces the RIMGEN (or RIMGEA) acronym to guide testers in writing better bug reports. We have created a set of printable cards with illustrations for each step of the bug investigation guide. You can download them here.

In this lecture, Kaner presents strategies to help testers explore non-reproducible bugs so they are reproducible. He also discusses how tracking non-reproducible bugs can help troubleshooting efforts.

This lecture focuses on overcoming objections, by understanding why a bug could be rejected. You will go through a list of reasons why programmers might resist spending time on a bug and how your investigation and reporting efforts can influence this for the better.

In addition to the quality of bug reports, a tester’s actions can influence how much credibility and influence they have on a project. This lecture draws on research on bias and signal detection theory to explore some of the things that enhance or diminish a tester’s credibility.

This lesson provides a structure for organizing your thinking about the many test techniques, and a focus on testing tours and on function testing.

This lecture introduces risk-based testing (including failure mode analysis and quicktests) and also a few concepts important for developing a testing strategy.

This lecture introduces specification-based testing and suggests eight questions that can guide specifications analysis.

This lecture introduces scenario testing, including 17 approaches to creating suites of scenario tests. It also suggests comparing test techniques in terms of their core strengths.

This lecture introduces domain testing, the most popular test technique. The lecture presents a schema for applying domain testing that emphasizes the technique’s roots in risk-based testing.

This lecture focuses on ways to test several variables together, emphasizing combinatorial approaches (such as all-pairs).