Issue test cases
C C++ Other
Latest commit 596d89c Oct 6, 2015 @xaqq xaqq Merge pull request #15 from kondrenkov/master
Added testcase for #1588
Permalink
Failed to load latest commit information.
140/2-1 Added test case for 140 Sep 2, 2011
1588
188/2-1
191 Added link back to issue Apr 30, 2011
199 Removed binaries, should not have been in git May 1, 2011
207 Added test case for 207 Aug 30, 2011
209 Improved the blaster Jun 9, 2011
218 Added 3.0 test version Sep 2, 2011
228 Added testcase for 228 Jul 13, 2011
231/2-1 Moved to right place Jul 14, 2011
232
234/2-1 Added test case for issue 234 Jul 22, 2011
235 Merge branch 'master' of github.com:zeromq/issues Jul 30, 2011
236/2-1
255/3-0 fix include line Sep 17, 2011
256/3-0
270/3-0
281/2-1
290/2-1 Add test case for issue 290 Dec 6, 2011
293
308-309
325 Test case for issue #325 May 28, 2012
334
337 Finished test case Mar 20, 2012
345 Test case for issue #345 Mar 22, 2012
346 Made test case for issue #346 Mar 22, 2012
369
431 Test case for issue #341 Oct 19, 2012
451 Added test cases for 451, 459 Nov 15, 2012
456 determine whether issue 456 has been resolved Oct 27, 2012
459 Added test cases for 451, 459 Nov 15, 2012
470 Added test case for issue #470 Nov 18, 2012
471
479 Test case for #479 - fixed Dec 11, 2012
487 Added test case for issue 487 Dec 22, 2012
507/3-2
508/3-2 repro code for issues 507, 508 and 509 Feb 19, 2013
509/3-2 repro code for issues 507, 508 and 509 Feb 19, 2013
511 Test for issue 511 - zmq_getsockopt for ZMQ_RCVMORE gives 0 before la… Feb 26, 2013
512
525
526
554 Move linger test to issue repo. Nov 25, 2013
562
566
574
578
757 Fixed message loss on close issue Nov 19, 2013
763
84 Added testcase for LIBZMQ-84 Jan 1, 2013
872
896 Added test case for #896 Feb 16, 2014
.gitignore
README Added issues 191 and 199 Apr 30, 2011

README

This is the git repo for issue test cases

Each issue has a subdirectory named 'nnn' where that is the issue number.

Within that subdirectory, there should directories 2-1 and 3-0 for version-specific test cases.

Please add a README to each issue indicating how to run the tests and what results are expected.