Lumiera  0.pre.03
»edit your freedom«
EventLog_test Class Reference

Description

Test:
verify a logging facility, which can be used to ensure some events happened while running test code.
  • various kinds of events or function calls are logged via the logging API.
  • within the test code, a match is performed against the contents of the log, using a DSL to represent matches relative to other matches
  • when a match fails, additional diagnostics are printed to STDERR
    See also
    event-log.hpp

Definition at line 52 of file event-log-test.cpp.

Private Member Functions

void run (Arg)
 
void verify_backwardMatch ()
 
void verify_callLogging ()
 
void verify_eventLogging ()
 
void verify_genericLogging ()
 
void verify_logJoining ()
 
void verify_logPurging ()
 
void verify_negatedMatch ()
 
void verify_regExpMatch ()
 
void verify_simpleUsage ()
 

Member Function Documentation

◆ verify_logJoining()

void verify_logJoining ( )
inlineprivate
Test:
combining several logs The EventLog objects are actually just lightweight front-end handles, while the actual log lives on the Heap.

This allows to have several handles hold onto the same actual log; this way, we can access and verify logs even after the managing object is destroyed.

The "log joining" functionality covered here is just an obvious extension to this setup: it allows to attach one log to another log after the fact; the contents of the joined log are integrated into the target log.

Remarks
this functionality is "low hanging fruit" – not sure if it's useful.

Definition at line 141 of file event-log-test.cpp.

References EventMatch::after(), EventMatch::before(), EventLog::ensureNot(), EventLog::event(), EventLog::joinInto(), and EventLog::verify().

+ Here is the call graph for this function:
+ Inheritance diagram for EventLog_test:
+ Collaboration diagram for EventLog_test:

The documentation for this class was generated from the following file: