This documentation is structured by what you, as a user, need to know to successfully use the Unit Test Framework and the order of decisions you have to make and order of complexity of the problems you might encounter. If you ever find yourself facing with some unclear term feel free to jump directly to the glossary section, where short definitions for all used terms were collected.
Typically, when writing a test module using the Unit Test Framework you have to go through the following steps:
#include it as a header-only
library, or link with it as a static library, or use it as a shared (or
dynamically loaded) library. For details on this topic see section Usage variants.
If you can't find answer to your question in any of the section mentioned above or if you believe you need even more configuration options, you can check Advanced usage scenarios section.