Available courses

This is an introductory survey of test design. The course introduces you to:

  • many techniques at a superficial level (what the technique is);
  • a few techniques at a practical level (how to do it);
  • ways to mentally organize this collection of techniques; 
  • using the the Heuristic Test Strategy Model for test planning and design: and
  • using concept mapping tools for test planning. 

Any of these techniques can be used in a scripted way or an exploratory way.

This course is a prerequisite for all other courses in the Black Box Software Testing (BBST®) series. In this course, we address:

  • How to succeed in online classes
  • Fundamental concepts and definitions
  • Fundamental challenges in software testing

This course is designed for individuals interested in learning to teach using the Black Box Software Testing materials developed by Cem Kaner. If you have completed one of the BBST® courses and want to teach courses using this model, we invite you to complete this course.

The course focuses on the BBST® four-week Professional Development model used by Florida Institute of Technology and the Association for Software Testing. However, you can apply most of the principles developed for this course to both academic or commercial settings and a variety of course formats; face-to-face, online, or a hybrid of both.

Bug reports are not just neutral technical reports. They are persuasive documents. The key goal of the bug report author is to provide high-quality information, well written, to help stakeholders make wise decisions about which bugs to fix. Key aspects of the content of this course include:

  • Defining key concepts (such as software error, quality, and the bug processing workflow)
  • the scope of bug reporting (what to report as bugs, and what information to include)
  • Bug reporting as persuasive writing
  • Bug investigation to discover harsher failures and simpler replication conditions
  • Excuses and reasons for not fixing bugs
  • Making bugs reproducible
  • Lessons from the psychology of decision-making: bug-handling as a multiple-decision process dominated by heuristics and biases.
  • Style and structure of well-written reports

Our learning objectives include this content, plus improving your abilities / skills to:

  • evaluate bug reports written by others
  • revise / strengthen reports written by others
  • write more persuasively (considering the interests and concerns of your audience)
  • participate effectively in distributed, multinational workgroup projects that are slightly more complex than the one in BBST-Foundations