- 24 Mar, 2019 1 commit
-
-
Simon Giesecke authored
Solution: define setUp/tearDown functions via SETUP_TEARDOWN_TESTCONTEXT macro where possible
-
- 23 Mar, 2019 1 commit
-
-
Simon Giesecke authored
Solution: remove and add where needed
-
- 27 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: apply naming style
-
- 25 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: added tests
-
- 14 May, 2018 5 commits
-
-
Luca Boccassi authored
Solution: re-enable them
-
Simon Giesecke authored
Solution: migrate to unity assertions
-
Luca Boccassi authored
Solution: if a PING message contains a context, echo it back in the PONG message. In order to do so, create the PONG message when PING is received and store it in the engine. After the PING the engine goes straight to encoding and sending, so there can always be at most one pending PING. Add tests for various contexts.
-
Luca Boccassi authored
Solution: remove it, it doesn't add much value anyway
-
Simon Giesecke authored
Solution: migrate to unity
-
- 28 Apr, 2018 1 commit
-
-
Luca Boccassi authored
Solution: check more socket type to cover other session managers. Increase timeout as the test now takes ~12 seconds.
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 13 Jun, 2017 1 commit
-
-
Luca Boccassi authored
Solution: revert change that made ZAP mandatory. The "Stonehouse" pattern, where CURVE is used only for encryption and without authentication, is a valid use case so we should still support it. Also restore CURVE testing in the test_heartbeat. Fixes #2594
-
- 01 May, 2017 1 commit
-
-
Luca Boccassi authored
Solution: use ZMQ_LAST_ENDPOINT in most places. This alllows running tests in paralle, and on over-booked shared machines where many of the ports would be already in use. Keep 3 tests with an hardcoded port, as there are some code paths that require it (eg: connect before bind), but list those ports in tests/testutil.hpp as macros so that they do not overlap and still allow parallel runs. These changes were inspired by a patch uploaded to Ubuntu by the package maintainer, Steve Langasek <steve.langasek@ubuntu.com>. Thank you Steve!
-
- 30 Mar, 2017 1 commit
-
-
evoskuil authored
-
- 13 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: use msleep (SETTLE_TIME) everywhere when waiting for the connections/sockets to be settled instead of a variety of patterns and functions to make tests more coherent.
-
- 12 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
There were numerous small issues with test cases: - some lacked the right source file header - some were not portable at all - some were using internal libzmq APIs (headers) Solution: fixed and cleaned up.
-
- 06 Feb, 2016 2 commits
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 28 Jul, 2015 1 commit
-
-
Brian Silverman authored
Under linux 3.16.0-4-amd64, I was getting occasional test failures before fixing this.
-
- 26 Jun, 2015 1 commit
-
-
Jonathan Reams authored
Set the ZMQ_HEARTBEAT_TIMEOUT to default to the value of ZMQ_HEARTBEAT_IVL if it's not explicitly set. Change the units of ZMQ_HEARTBEAT_TTL to milliseconds in the API and round down to the nearest decisecond so that all the options are using the same units. Make the maximum heartbeat TTL match the spec (6553 seconds)
-
- 24 Jun, 2015 2 commits
-
-
Jonathan Reams authored
-
Jonathan Reams authored
This commit adds ZMTP connection heartbeats described in http://rfc.zeromq.org/spec:37/ZMTP.
-