LUMIERA.clone/tests/steam/control/test-dummy-commands.cpp
Ichthyostega 3caa5cfb03 Tests: reorganise test folders
This resolves a long-standing issue:
we could not use proper include paths for test-helper code that was defined alongside the tests.

Since some test-helper code must now be relocated into the »Vault«-Layer,
I took the opportunity to finally resolve this annoyance. The solution is two-fold
 * introduce a dedicated test-support library
 * remove the quirks that were necessary to support some plain-C tests
Together, this allows to raise the include-directory by one level,
and then to adjust all folder names so that they match the namespace
2026-03-07 00:56:19 +01:00

80 lines
1.9 KiB
C++
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

/*
test-dummy-commands - global checksum variables used to build test commands
Copyright (C)
2009, Hermann Vosseler <Ichthyostega@web.de>
  **Lumiera** is free software; you can redistribute it and/or modify it
  under the terms of the GNU General Public License as published by the
  Free Software Foundation; either version 2 of the License, or (at your
  option) any later version. See the file COPYING for further details.
* *****************************************************************/
/** @file test-dummy-commands.cpp
** Implementation of dummy command operations for unit tests
*/
#include "steam/control/test-dummy-commands.hpp"
#include "steam/control/command-def.hpp"
namespace steam {
namespace control {
namespace test {
namespace command1 {
int64_t check_ = 0;
}
namespace command2 {
ostringstream check_;
}
namespace command3 {
ulong check_;
}
/* ==== global static prototype definitions for these commands ==== */
/**
* @remark The following definition(s) will be evaluated automatically ON_GLOBAL_INIT
* They result in "prototype" definitions of these dummy commands to be
* registered under the names as used here in the macro invocation.
* Thus `test_Dummy_command1` will invoke command1::operate(int) etc.
* @see CommandSetup_test
*/
COMMAND_DEFINITION (test_Dummy_command1)
{
def.operation(command1::operate)
.captureUndo(command1::capture)
.undoOperation(command1::undoIt);
};
COMMAND_DEFINITION (test_Dummy_command2)
{
def.operation(command2::operate)
.captureUndo(command2::capture)
.undoOperation(command2::undoIt);
};
COMMAND_DEFINITION (test_Dummy_command3)
{
def.operation(command3::operate)
.captureUndo(command3::capture)
.undoOperation(command3::undoIt);
};
}}} // namespace steam::control::test