Chiebot-Mirror/c-ares - c-ares - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Gregor Jasny	e8ab6b53bf	Embed fused Google Test 1.8.0	7 years ago
David Drysdale	a4a0d2fb7e	test: distribute the fuzzcheck.sh script The TESTS target runs fuzzcheck.sh so make sure it is included in the distributed tarball. (The test itself will be pointless when run on a distribution, because the fuzzing corpus directories are not shipped, but at least this means that `make -C test test` should work.)	8 years ago
David Drysdale	8fdd3d3d19	test: add fuzz entrypoint for ares_create_query()	8 years ago
David Drysdale	d6823a5cf3	test: Add gTest/gMock files to SOURCES Built tarballs are not including all of the files needed to build the test suite because they are missing from the <target>_SOURCES variable in Makefile.am.	8 years ago
David Drysdale	2401623710	test: add fuzzing check script to tests Add a test script that runs the fuzzing command over the corpus of DNS packets. This doesn't actually do any fuzzing (it just runs them as inputs without generating any variations) but it does ensure that the fuzzing entrypoint is still working.	9 years ago
David Drysdale	b701af8a24	test: Add utility to show DNS packet from file	9 years ago
David Drysdale	d3bccff740	test: Move file lists into Makefile.inc In preparation for a Win32 build of the test suite.	9 years ago
David Drysdale	3ce586feb7	test: Remove duplicate flags from Makefile.am	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	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