~/talk

C++ Unit testing - the good, the bad & the ugly

Talkat NDC Oslo 2017 · 2017-06-14..06-16· [testing]
slides:none on file

Argues that C++ defects like memory leaks and out‑of‑bounds errors get caught early by unit tests and shows concrete tool choices: Google Test + Google Mock (must build matching configs, needs virtual methods), Catch header-only and Sections (string test names, continue/check vs require), and alternatives (doctest, Boost.Test, CppUnit, metal, trompeloeil, FakeIt). Demonstrates mock setup patterns, Visual Studio test runners and coverage, explains header‑only deployment vs compiled libs, and insists on CI to run tests reliably.

AI-written summary · about

  1. 0:00Introduction and speaker
  2. 1:21Why use C++
  3. 3:59The challenges of C++
  4. 5:05Benefits of unit testing
  5. 8:43Defining unit tests
  6. 11:53Structure of a test
  7. 13:29Essential testing tools
  8. 15:48Framework components
  9. 17:18Overview of C++ frameworks
  10. 24:46Framework examples
  11. 33:42Test design patterns
  12. 43:03Mocking frameworks
  13. 52:42Conclusion and Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.