![]() |
ChimeraTK-ApplicationCore 04.06.00
|
#include "Application.h"#include "ApplicationModule.h"#include "check_timeout.h"#include "DeviceModule.h"#include "ScalarAccessor.h"#include "TestFacility.h"#include <ChimeraTK/BackendFactory.h>#include <ChimeraTK/Device.h>#include <ChimeraTK/DummyRegisterAccessor.h>#include <ChimeraTK/ExceptionDummyBackend.h>#include <boost/mpl/list.hpp>#include <boost/test/included/unit_test.hpp>#include <VoidAccessor.h>#include <chrono>#include <functional>#include <future>
Include dependency graph for testInitialValueSpecD8.cc:Go to the source code of this file.
Namespaces | |
| namespace | Tests |
| namespace | Tests::testInitialValues |
Macros | |
| #define | BOOST_TEST_MODULE testInitialValues |
Typedefs | |
| using | Tests::testInitialValues::DeviceTestApplicationTypes = boost::mpl::list< PushDummyApplication, PollDummyApplication > |
Test Initial Values - Inputs of ApplicationModules InitialValuesInputsOfApplicationCore_D_8 "D.8". | |
| using | Tests::testInitialValues::TestInputTypes = boost::mpl::list< ctk::ScalarPollInput< int >, ctk::ScalarPushInput< int > > |
Functions | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE_TEMPLATE (testInitValueAtDevice8bi, APPLICATION_TYPE, DeviceTestApplicationTypes) | |
| For device variables the ExceptionHandlingDecorator freezes the variable until the device is available initialValue_D_8_b_i. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE_TEMPLATE (testProcessArrayInitValueAtDevice8bii, INPUT_TYPE, TestInputTypes) | |
| ProcessArray freeze in their implementation until the initial value is received initialValue_D_8_b_ii. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE_TEMPLATE (testConstantInitValueAtDevice8biii, INPUT_TYPE, TestInputTypes) | |
Constants can be read exactly once in case of AccessMode::wait_for_new_data, so the initial value can be received. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testPushInitValueAtDeviceD9) | |
| D 9 b for ThreadedFanOut initialValueThreadedFanOut_D_9_b. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testTriggerFanOutInitValueAtDeviceD9) | |
| D 9 b for TriggerFanOut initialValueThreadedFanOut_D_9_b. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testConstantD10InitialValue) | |
| D 10 for Constant initialValue_d_10. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD1InitialValue) | |
| D 1 for DataValidity::faulty testD1InitialValue_D_1. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD2InitialValue) | |
| D 2 for DataValidity::faulty testD1InitialValue_D_2. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD3InitialValue) | |
| D 3 for DataValidity::faulty testD1InitialValue_D_3. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD7_1_InitialValue) | |
| D 7_1 testD7_1_InitialValue. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD7_2_InitialValue) | |
| D 7_2 testD7_2_InitialValue. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD6_a1_InitialValue) | |
| D 6_a1 initial value from control system variable testD6_a1_InitialValue. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD6_a2_InitialValue) | |
| D 6_a2 initial value from device in poll mode testD6_a2_InitialValue. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD6_a3_InitialValue) | |
| D 6_a3 initial value from device in push mode testD6_a3_InitialValue. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD6_a4_InitialValue) | |
| D 6_a4 initial value from output testD6_a4_InitialValue. | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD6_b_InitialValue) | |
| D 6_b initial value from device in poll mode testD6_b_InitialValue FIXME: Is this supposed to test push variables in poll mode or poll variables? | |
| Tests::testInitialValues::BOOST_AUTO_TEST_CASE (testD6_c_InitialValue) | |
| D 6_c initial value from device in push mode testD6_c_InitialValue. | |
| #define BOOST_TEST_MODULE testInitialValues |
Definition at line 3 of file testInitialValueSpecD8.cc.