path: root/test/README
diff options
Diffstat (limited to 'test/README')
1 files changed, 4 insertions, 6 deletions
diff --git a/test/README b/test/README
index 401f5d7e95f2..dc0afd80a8d9 100644
--- a/test/README
+++ b/test/README
@@ -1,6 +1,4 @@
-when you build, gdb will start with the cppunit test loaded, type "run" to execute the test under gdb.
-If you have consistent test failures on testCVEs, that probably means your antivirus is blocking the test files (as they are known to be exploits of fixed security issues). You may want to disable the monitoring of <root of repo>\*\pass in your AV.
-A top-level "make check" will first do a full build, then run all the subsequent tests, while a top-level "make subsequentcheck" will only run all the subsequent tests. You can run a single subsequent test via its target
-There will be a log file of the failed test, you can look at it with a text editor:
-The log file will contain a Java stack trace of the failed test \ No newline at end of file
+Test harness code for C++ unit testing
+Many of these tests are run during the build process. In that case on
+unix, if a test fails follow the error messages to debug it under gdb.