lumiera_documentation/tests/library/sync-waiting-test.cpp
Ichthyostega 9c74466778 Tests: build an link a test-support library
This is something I wanted to clean-up since a very long time indeed,
but always postponed it, since it requires a lot of nasty clean-up and disentangling....

Several parts had been stashed away into `src/lib/test`, which are not really related:
 * the testrunner and testsuite builder
 * generic helper utilities
 * specialised test-support facilities, e.g. the EventLog

This changeset introduces a new top-level test folder and a namespace `::test`
Code from this folder is linked into a shared library `libtestsupport.so`,
which resides in the linkage hierarchy between »Vessel« and »Vault«,
yet is no longer part of the Lumiera application and only linked into the test-suite.
2026-03-06 23:16:32 +01:00

118 lines
3.1 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.

/*
SyncWaiting(Test) - check the monitor object based wait/notification
Copyright (C)
2008, 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 sync-waiting-test.cpp
** unit test \ref SyncWaiting_test
*/
#include "test/run.hpp"
#include "lib/error.hpp"
#include "lib/thread.hpp"
#include "lib/sync.hpp"
#include <atomic>
using test::Test;
using std::atomic_uint;
using std::atomic_bool;
using std::this_thread::sleep_for;
using std::chrono_literals::operator ""ms;
namespace lib {
namespace test{
namespace { // test subject...
/** demonstrates how to wait on a simple boolean flag */
class SyncOnBool
: public Sync<NonrecursiveLock_Waitable>
{
atomic_uint sum_{0}, input_{0};
atomic_bool got_new_data_{false};
public:
void getIt()
{
Lock await{this, [&]{ return bool(got_new_data_); }};
sum_ += input_;
}
void provide (uint val)
{
Lock sync{this};
input_ = val;
got_new_data_ = true;
sync.notify_all();
}
/** harvesting the result...*/
uint result () { return sum_; }
};
}//(End) test subject.
/************************************************************************//**
* @test concurrent waiting and notification, implemented via object monitor.
* This test covers the second part of the monitor pattern, which builds upon
* the locking part, additionally using an embedded condition. Two interwoven
* threads are created, both blocked until a start value is given. Once awakened,
* each thread should add the start value to a common sum field.
* @see SyncLocking_test
* @see sync.hpp
*/
class SyncWaiting_test : public Test
{
virtual void
run (Arg)
{
seedRand();
SyncOnBool token;
ThreadJoinable ping ("SyncWaiting ping", [&]{ token.getIt(); });
ThreadJoinable pong ("SyncWaiting pong", [&]{ token.getIt(); });
CHECK (ping);
CHECK (pong);
CHECK (0 == token.result());
sleep_for (100ms); // if the threads don't block correctly, they've missed their chance by now...
// kick off the notification cascade...
uint val = rani(1000);
token.provide (val);
// wait for the two Threads to finish their handshake
pong.join();
ping.join();
CHECK (2*val == token.result());
}
};
/** Register this test class... */
LAUNCHER (SyncWaiting_test, "unit common");
}} // namespace lib::test