c-ares

Commit Graph

Author	SHA1	Message	Date
David Drysdale	25adcc413e	test: more tests, especially fallback processing - Make mock server listen on UDP + TCP in parallel. - Test UDP->TCP fallback on truncation - Test EDNS->no-EDNS fallback - Test some environment init options - Test nonsense reply test: short response	9 years ago
David Drysdale	a05f240dea	test: more tests, particularly of initialization	9 years ago
David Drysdale	83839fde7a	test: Run mock tests over both TCP and UDP With the exception of a few tests that make use of the timed retry aspect of UDP.	9 years ago
David Drysdale	0c423efd78	test: Run mock tests over both IPv4 and IPv6	9 years ago
David Drysdale	0ef56333a0	test: Add more tests for edge cases	9 years ago
David Drysdale	a2c5b1d378	test: Use of HOSTALIAS environment variable	9 years ago
David Drysdale	693e566b66	test: More search domain scenarios	9 years ago
David Drysdale	6589ebfd6a	test: Make test code leak-free	9 years ago
David Drysdale	4a09121923	test: More tests - test use of sortlist - test gethostbyname(AF_UNSPEC)	9 years ago
David Drysdale	ffc7c52656	test: Tweak tests, add alloc failure test	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

11 Commits (25adcc413e3fe8869f923a498691f0e1a559bfb1)