X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=ceph%2Fsrc%2Fjaegertracing%2Fopentelemetry-cpp%2Fthird_party%2Fprometheus-cpp%2F3rdparty%2Fcivetweb%2Ftest%2FREADME.md;fp=ceph%2Fsrc%2Fjaegertracing%2Fopentelemetry-cpp%2Fthird_party%2Fprometheus-cpp%2F3rdparty%2Fcivetweb%2Ftest%2FREADME.md;h=49f2245df695b55769e3c447cc024b92ff9169ba;hb=1e59de90020f1d8d374046ef9cca56ccd4e806e2;hp=0000000000000000000000000000000000000000;hpb=bd41e436e25044e8e83156060a37c23cb661c364;p=ceph.git

diff --git a/ceph/src/jaegertracing/opentelemetry-cpp/third_party/prometheus-cpp/3rdparty/civetweb/test/README.md b/ceph/src/jaegertracing/opentelemetry-cpp/third_party/prometheus-cpp/3rdparty/civetweb/test/README.md
new file mode 100644
index 000000000..49f2245df
--- /dev/null
+++ b/ceph/src/jaegertracing/opentelemetry-cpp/third_party/prometheus-cpp/3rdparty/civetweb/test/README.md
@@ -0,0 +1,25 @@
+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`