Pawel Kurdybacha 57454dff4b Problem: monitor_t tests not event driven ...

Solution: instead of waiting for fixed amount of time for events, react
as soon as events are triggered.

- Total running time of unittest reduced 10x (from ~300ms to 30ms).
- Reduced code duplication by reusing testutil's constructs.

2018-07-05 00:23:31 +01:00

..

cmake

Problem: googletest is also installed into install destination

2018-04-29 12:57:32 +01:00

active_poller.cpp

Problem: whitespace style too restrictive.

2018-05-12 17:28:28 +01:00

CMakeLists.txt

Problem: no test case for zmq::monitor_t::init

2018-06-05 17:27:28 +02:00

context.cpp

Problem: whitespace style too restrictive.

2018-05-12 17:28:28 +01:00

main.cpp

Problem: whitespace style too restrictive.

2018-05-12 17:28:28 +01:00

message.cpp

Add message_t::routing_id() and set_routing_id()

2018-05-19 08:44:41 +03:00

monitor.cpp

Problem: monitor_t tests not event driven

2018-07-05 00:23:31 +01:00

multipart.cpp

Problem: whitespace style too restrictive.

2018-05-12 17:28:28 +01:00

poller.cpp

Problem: whitespace style too restrictive.

2018-05-12 17:28:28 +01:00

socket.cpp

Problem: whitespace style too restrictive.

2018-05-12 17:28:28 +01:00

testutil.hpp

Problem: monitor_t tests not event driven

2018-07-05 00:23:31 +01:00