From c9edda1cf80b85c7d5d66e27bfede6ed3892ba0c Mon Sep 17 00:00:00 2001
From: Alan Conway <aconway@apache.org>
Date: Mon, 2 Apr 2007 21:22:33 +0000
Subject: Updated to point to tests/README.

git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid@524927 13f79535-47bb-0310-9956-ffa450edef68
---
 cpp/README | 25 ++-----------------------
 1 file changed, 2 insertions(+), 23 deletions(-)

(limited to 'cpp/README')

diff --git a/cpp/README b/cpp/README
index 83e9d6ed5e..295d27d279 100644
--- a/cpp/README
+++ b/cpp/README
@@ -233,30 +233,9 @@ implementation sufficient for the client using the APR portability
 library. The implementations may change in future but the interface
 for qpid code outside the qpid/sys namespace should remain stable.
 
-=== Unit tests ===
+=== Tests ===
 
-Unit tests are built as .so files containing CppUnit plugins.
-
-DllPlugInTester is provided as part of cppunit. You can use it to run
-any subset of the unit tests. See Makefile for examples.
-
-NOTE: If foobar.so is a test plugin in the current directory then
-surprisingly this will fail with "can't load plugin":
- # DllPluginTester foobar.so
-
-Instead you need to say:
- # DllPluginTester ./foobar.so
-
-Reason: DllPluginTester uses dlopen() which only searches for shlibs
-in the standard places unless the filename contains a "/".  In that
-case it just tries to open the filename.
-
-=== System tests ===
-
-The Python test suite ../python/run_tests is the main set of broker
-system tests.
-
-There are some C++ client test executables built under client/test.
+See src/tests/README for details.
 
 == Doxygen ==
 
-- 
cgit v1.2.1