nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-14 07:03:44 +01:00
Code Issues Packages Projects Releases Wiki Activity
a50690e68f
tor/src/ext/tinytest_macros.h

185 lines
6.4 KiB
C
Raw Normal View History

Synchronize with upstream tinytest. The big change here is a patch (first added to Libevent by Ed Day) to make sure that the CreateProcess forked-test trick works even when the main test program is invoked without its .exe suffix.
2012-02-13 23:28:15 +01:00
/* tinytest_macros.h -- Copyright 2009-2012 Nick Mathewson
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. The name of the author may not be used to endorse or promote products
* derived from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
#ifndef TINYTEST_MACROS_H_INCLUDED_
#define TINYTEST_MACROS_H_INCLUDED_
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
/* Helpers for defining statement-like macros */
#define TT_STMT_BEGIN do {
Update to the latest tinytest version This cleans up some whitespace consistency issues and, more importantly, gives you the ability to skip tests from the command line.
2010-09-09 20:34:10 +02:00
#define TT_STMT_END } while (0)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
/* Redefine this if your test functions want to abort with something besides
* "goto end;" */
#ifndef TT_EXIT_TEST_FUNCTION
#define TT_EXIT_TEST_FUNCTION TT_STMT_BEGIN goto end; TT_STMT_END
#endif
/* Redefine this if you want to note success/failure in some different way. */
#ifndef TT_DECLARE
#define TT_DECLARE(prefix, args) \
TT_STMT_BEGIN \
printf("\n %s %s:%d: ",prefix,__FILE__,__LINE__); \
printf args ; \
TT_STMT_END
#endif
Update to the latest tinytest version This cleans up some whitespace consistency issues and, more importantly, gives you the ability to skip tests from the command line.
2010-09-09 20:34:10 +02:00
/* Announce a failure. Args are parenthesized printf args. */
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#define TT_GRIPE(args) TT_DECLARE("FAIL", args)
/* Announce a non-failure if we're verbose. */
#define TT_BLATHER(args) \
TT_STMT_BEGIN \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
if (tinytest_get_verbosity_()>1) TT_DECLARE(" OK", args); \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
TT_STMT_END
#define TT_DIE(args) \
TT_STMT_BEGIN \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tinytest_set_test_failed_(); \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
TT_GRIPE(args); \
TT_EXIT_TEST_FUNCTION; \
TT_STMT_END
#define TT_FAIL(args) \
TT_STMT_BEGIN \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tinytest_set_test_failed_(); \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
TT_GRIPE(args); \
TT_STMT_END
/* Fail and abort the current test for the reason in msg */
Oops; there were a couple of typos in the upstream tinytest
2012-02-13 23:48:43 +01:00
#define tt_abort_printf(msg) TT_DIE(msg)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#define tt_abort_perror(op) TT_DIE(("%s: %s [%d]",(op),strerror(errno), errno))
#define tt_abort_msg(msg) TT_DIE(("%s", msg))
#define tt_abort() TT_DIE(("%s", "(Failed.)"))
/* Fail but do not abort the current test for the reason in msg. */
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
#define tt_failprint_f(msg) TT_FAIL(msg)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#define tt_fail_perror(op) TT_FAIL(("%s: %s [%d]",(op),strerror(errno), errno))
#define tt_fail_msg(msg) TT_FAIL(("%s", msg))
#define tt_fail() TT_FAIL(("%s", "(Failed.)"))
/* End the current test, and indicate we are skipping it. */
Update to the latest tinytest version This cleans up some whitespace consistency issues and, more importantly, gives you the ability to skip tests from the command line.
2010-09-09 20:34:10 +02:00
#define tt_skip() \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
TT_STMT_BEGIN \
Oops; there were a couple of typos in the upstream tinytest
2012-02-13 23:48:43 +01:00
tinytest_set_test_skipped_(); \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
TT_EXIT_TEST_FUNCTION; \
TT_STMT_END
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
#define tt_want_(b, msg, fail) \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
TT_STMT_BEGIN \
if (!(b)) { \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tinytest_set_test_failed_(); \
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
TT_GRIPE(("%s",msg)); \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
fail; \
} else { \
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
TT_BLATHER(("%s",msg)); \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
} \
TT_STMT_END
/* Assert b, but do not stop the test if b fails. Log msg on failure. */
#define tt_want_msg(b, msg) \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tt_want_(b, msg, );
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
/* Assert b and stop the test if b fails. Log msg on failure. */
#define tt_assert_msg(b, msg) \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tt_want_(b, msg, TT_EXIT_TEST_FUNCTION);
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
/* Assert b, but do not stop the test if b fails. */
#define tt_want(b) tt_want_msg( (b), "want("#b")")
/* Assert b, and stop the test if b fails. */
#define tt_assert(b) tt_assert_msg((b), "assert("#b")")
#define tt_assert_test_fmt_type(a,b,str_test,type,test,printf_type,printf_fmt, \
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
setup_block,cleanup_block,die_on_fail) \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
TT_STMT_BEGIN \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
type val1_ = (type)(a); \
type val2_ = (type)(b); \
int tt_status_ = (test); \
if (!tt_status_ || tinytest_get_verbosity_()>1) { \
printf_type print_; \
printf_type print1_; \
printf_type print2_; \
type value_ = val1_; \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
setup_block; \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
print1_ = print_; \
value_ = val2_; \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
setup_block; \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
print2_ = print_; \
TT_DECLARE(tt_status_?" OK":"FAIL", \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
("assert(%s): "printf_fmt" vs "printf_fmt, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
str_test, print1_, print2_)); \
print_ = print1_; \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
cleanup_block; \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
print_ = print2_; \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
cleanup_block; \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
if (!tt_status_) { \
tinytest_set_test_failed_(); \
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
die_on_fail ; \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
} \
} \
TT_STMT_END
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
#define tt_assert_test_type(a,b,str_test,type,test,fmt,die_on_fail) \
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
{print_=value_;},{},die_on_fail)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
/* Helper: assert that a op b, when cast to type. Format the values with
* printf format fmt on failure. */
#define tt_assert_op_type(a,op,b,type,fmt) \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tt_assert_test_type(a,b,#a" "#op" "#b,type,(val1_ op val2_),fmt, \
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
TT_EXIT_TEST_FUNCTION)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#define tt_int_op(a,op,b) \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
"%ld",TT_EXIT_TEST_FUNCTION)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#define tt_uint_op(a,op,b) \
tt_assert_test_type(a,b,#a" "#op" "#b,unsigned long, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
(val1_ op val2_),"%lu",TT_EXIT_TEST_FUNCTION)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#define tt_ptr_op(a,op,b) \
tt_assert_test_type(a,b,#a" "#op" "#b,void*, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
(val1_ op val2_),"%p",TT_EXIT_TEST_FUNCTION)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#define tt_str_op(a,op,b) \
tt_assert_test_type(a,b,#a" "#op" "#b,const char *, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
(strcmp(val1_,val2_) op 0),"<%s>",TT_EXIT_TEST_FUNCTION)
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
#define tt_want_int_op(a,op,b) \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_),"%ld",(void)0)
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
#define tt_want_uint_op(a,op,b) \
tt_assert_test_type(a,b,#a" "#op" "#b,unsigned long, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
(val1_ op val2_),"%lu",(void)0)
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
#define tt_want_ptr_op(a,op,b) \
tt_assert_test_type(a,b,#a" "#op" "#b,void*, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
(val1_ op val2_),"%p",(void)0)
Upgrade to the latest version of tinytest
2011-06-09 23:30:09 +02:00
#define tt_want_str_op(a,op,b) \
tt_assert_test_type(a,b,#a" "#op" "#b,const char *, \
Synchronize with upstream tinytest again: remove _identifiers
2012-02-13 23:45:15 +01:00
(strcmp(val1_,val2_) op 0),"<%s>",(void)0)
Refactor unit tests to use the tinytest framework. "Tinytest" is a minimalist C unit testing framework I wrote for Libevent. It supports some generally useful features, like being able to run separate unit tests in their own processes. I tried to do the refactoring to change test.c as little as possible. Thus, we mostly don't call the tinytest macros directly. Instead, the test.h header is now a wrapper on tinytest.h to make our existing test_foo() macros work. The next step(s) here will be: - To break test.c into separate files, each with its own test group. - To look into which things we can test - To refactor the more fiddly tests to use the tinytest macros directly and/or run forked. - To see about writing unit tests for things we couldn't previously test without forking.
2009-09-21 20:23:13 +02:00
#endif
Reference in New Issue Copy Permalink