1
0
mirror of https://github.com/lammertb/libhttp.git synced 2025-12-22 04:02:04 +03:00
Files
libhttp/test
bel a06ee625f5 Remove unit test for sdup in main.c
main.c is not a part of the CivetWeb library, but only a part of the standalone executable. Which part of main.c is used is heavily depending on the system, since there are a lot of #ifdef for Windows, Linux and OSX. Windows has some graphical user interface, implemented in main.c, while Linux has not. Most parts of main.c can not be tested automatically (with the given framwork), but only manually.
Including small parts of main.c into the automatic unit test will distort test statistics.
2016-05-21 01:21:54 +02:00
..
2016-04-16 21:53:15 +02:00
2016-04-16 21:53:15 +02:00
2012-05-05 17:32:54 +01:00
2016-04-18 21:11:39 +02:00
2014-02-22 22:48:49 +01:00
2015-03-23 16:38:15 +01:00
2012-07-27 06:24:11 +01:00
2014-04-11 22:08:24 +02:00
2015-11-27 20:10:10 +01:00
2016-01-11 20:28:50 +01:00
2015-08-12 21:50:38 +02:00
2015-08-12 21:50:38 +02:00
2014-01-02 00:17:13 +01:00
2016-03-19 22:58:18 +01:00
2015-01-04 22:10:46 +01:00
2015-08-24 22:31:50 +02:00
2015-08-24 22:31:50 +02:00
2013-12-24 10:58:48 +01:00
2015-10-12 21:23:59 +02:00
2016-05-06 22:59:06 +02:00
2015-07-25 19:51:24 +02:00
2016-05-15 23:46:12 +02:00
2015-07-09 21:05:37 +02:00
2016-05-06 22:59:06 +02:00
2010-12-07 12:38:11 +01:00
2015-04-06 23:52:37 +02:00
2012-09-22 13:31:10 +01:00

Testing

C API

The unit tests leverage the CTest and Check frameworks to provide a easy environment to build up unit tests. They are split into Public and Private test suites reflecting the public and internal API functions of civetweb.

When adding new functionality to civetweb tests should be written so that the new functionality will be tested across the continuous build servers. There are various levels of the unit tests:

  • Tests are included in
  • Test Cases which are there are multiple in
  • Test Suites which are ran by the check framework by
  • civetweb-unit-tests which is driven using the --suite and --test-case arguments by
  • CTest via add_test in CMakeLists.txt

Each test suite and test case is ran individually by CTest so that it provides good feedback to the continuous integration servers and also CMake. Adding a new test case or suite will require the corresponding add_test driver to be added to CMakeLists.txt