Part I. Boost Test Library: The Execution Monitor

| > The Execution Monitor > |

# Part I. Boost Test Library: The Execution Monitor

###

Sometimes we need to call a function and make sure that no user or system originated exceptions are being thrown by it. Uniform exception reporting is also may be convenient. That's the purpose of the Boost.Test's Execution Monitor.

The Execution Monitor is a lower-level component of the Boost Test Library. It is the base for implementing all other Boost.Test components, but also can be used standalone to get controlled execution of error-prone functions with a uniform error notification. The Execution Monitor calls a user-supplied function in a controlled environment, relieving users from messy error detection.

The Execution Monitor usage is demonstrated in the example exec_mon_example . Additional examples are in Part II, “The Program Execution Monitor” or Part IV, “The Unit Test Framework”.

#### Design Rationale

The Execution Monitor design assumes that it can be used when no (or almost no) memory available. Also the Execution Monitor is intended to be portable to as many platforms as possible.

Last revised: , at |