c-ares

Commit Graph

Author	SHA1	Message	Date
David Drysdale	ffc7c52656	test: Tweak tests, add alloc failure test	9 years ago
David Drysdale	e3434ef33f	test: Test init with options	9 years ago
David Drysdale	a48447ee27	test: More tests - ares_inet_net_pton() variants - ares_getsock() variants	9 years ago
David Drysdale	f9b9817d1d	test: Expose ProcessWork() function	9 years ago
David Drysdale	c778f0136b	test: More parsing tests Including: - Split each parse function test set out into separate files. - Add an allocation failure test for each parsing function. - Add error check test for each parsing function.	9 years ago
David Drysdale	79dc327a2d	test: Add various additional tests	9 years ago
David Drysdale	5da3201a05	test: More tests Include tests of internal functions, based on the value of the CARES_SYMBOL_HIDING macro; need to configure the library with --disable-symbol-hiding to enable these tests.	9 years ago
David Drysdale	3907b6dc68	test: Allow command line override of mock server port	9 years ago
David Drysdale	2aa07c7d02	test: Add README.md documentation	9 years ago
David Drysdale	af3ee9a8ba	test: Add initial unit tests for c-ares library The tests are written in C++11, using the GoogleTest and GoogleMock frameworks. They have their own independent autoconf setup, so that users of the library need not have a C++ compiler just to get c-ares working (however, the test/configure.ac file does assume the use of a shared top-level m4/ directory). However, this autoconf setup has only been tested on Linux and OSX so far. Run with "./arestest", or "./arestest -v" to see extra debug info. The GoogleTest options for running specific tests are also available (e.g. "./arestest --gtest_filter=Live"). The tests are nowhere near complete yet (currently hitting around 60% coverage as reported by gcov), but they do include examples of a few different styles of testing: - There are live tests (ares-test-live.cc), which assume that the current machine has a valid DNS setup and connection to the internet; these tests issue queries for real domains but don't particularly check what gets returned. The tests will fail on an offline machine. - There a few mock tests (ares-test-mock.cc) that set up a fake DNS server and inject its port into the c-ares library configuration. These tests allow specific response messages to be crafted and injected, and so are likely to be used for many more tests in future. - To make this generation/injection easier, the dns-proto.h file includes C++ helper classes for building DNS packets. - Other library entrypoints that don't require network activity (e.g. ares_parse__reply) are tested directly. - There are few tests of library-internal functions that are not normally visible to API users (in ares-test-internal.cc). - A couple of the tests use a helper method of the test fixture to inject memory allocation failures, using the earlier change to the library to allow override of malloc/realloc/free. - There is also an entrypoint to allow Clang's libfuzzer to drive the packet parsing code in ares_parse__reply, together with a standalone wrapper for it (./aresfuzz) to allow use of afl-fuzz for further fuzz testing.	9 years ago
David Drysdale	148b6e93b9	test: Add local copy of GoogleMock/GoogleTest 1.7.0 Don't check in gtest/m4 files, as they are unused and interfere with the top-level configure process.	9 years ago

1 2 3

112 Commits (ba1aa0635aa4e8f1f0fc99125931d88ed75bba68)