testDataValidityPropagation.cc File Reference

#include "Application.h"
#include "ApplicationModule.h"
#include "DeviceModule.h"
#include "ScalarAccessor.h"
#include "TestFacility.h"
#include <ChimeraTK/Device.h>
#include <ChimeraTK/DummyRegisterAccessor.h>
#include <ChimeraTK/ExceptionDummyBackend.h>
#include <ChimeraTK/NDRegisterAccessor.h>
#include <boost/mpl/list.hpp>
#include <chrono>
#include <cstring>
#include <boost/test/included/unit_test.hpp>

Include dependency graph for testDataValidityPropagation.cc:

Go to the source code of this file.

Classes
struct	Tests::testDataValidityPropagation::TestModule0
struct	Tests::testDataValidityPropagation::TestModule1
struct	Tests::testDataValidityPropagation::TestModule2
struct	Tests::testDataValidityPropagation::TriggerModule
struct	Tests::testDataValidityPropagation::TestApplication1< ModuleT >
struct	Tests::testDataValidityPropagation::TestApplication3
struct	Tests::testDataValidityPropagation::TestApplication16
	app with two chained modules, for testDataValidity_1_6 More...

Namespaces
namespace	Tests
namespace	Tests::testDataValidityPropagation

Macros
#define	BOOST_TEST_MODULE   testDataValidityPropagation
#define	BOOST_NO_EXCEPTIONS

Functions
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_1_3)
	1.3 If a device is in error state, all variables which are read from it shall be marked as 'faulty'.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_1_6)
	1.6 The user code can flag individual outputs as bad.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_1_8)
	1.8 The data validity of receiving variables is set to 'faulty' on construction.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_2_1_1)
	2.1.1 Each input and each output of a module (or fan out) is decorated with a MetaDataPropagatingRegisterDecorator (except for the TriggerFanOut, see.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_2_1_3)
	2.1.3 read: For each read operation it checks the incoming data validity and increases/decreases the data fault counter of the owner.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_2_3_1)
	2.3.1 Each ApplicationModule has one data fault counter variable which is increased/decreased by EntityOwner::incrementDataFaultCounter() and EntityOwner::decrementDataFaultCounter.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_2_3_3)
	2.3.3 The main loop of the module usually does not care about data validity.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_2_3_4)
	2.3.4 Inside the ApplicationModule main loop the module's data fault counter is accessible.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_2_4_1)
	2.4.1 Only the push-type trigger input of the TriggerFanOut is equiped with a MetaDataPropagatingRegisterDecorator.
	Tests::testDataValidityPropagation::BOOST_AUTO_TEST_CASE (testDataValidity_2_4_3)
	2.4.3 The individual poll-type inputs propagate the data validity flag only to the corresponding outputs.

Macro Definition Documentation

BOOST_NO_EXCEPTIONS

#define BOOST_NO_EXCEPTIONS

Definition at line 22 of file testDataValidityPropagation.cc.

BOOST_TEST_MODULE

#define BOOST_TEST_MODULE   testDataValidityPropagation

Definition at line 3 of file testDataValidityPropagation.cc.