diff options
| author | Alia Almusaireae <almusaireae@kacst.edu.sa> | 2012-11-05 13:47:35 +0300 |
|---|---|---|
| committer | Michael Meeks <michael.meeks@suse.com> | 2012-11-05 11:53:53 +0000 |
| commit | 4aed4f436cf8e4b0f3f034dfb1d1025b05a61f0a (patch) | |
| tree | 739af6bdee7b51e5835031defeb3308c9919a524 /test/README | |
| parent | b0d37e7f010bc159585e20c2792dcb9c4f3863c8 (diff) | |
add a README files
Change-Id: I4bd9a7d00df220e2a3deae3cc1b7b0f4a1098e24
Reviewed-on: https://gerrit.libreoffice.org/989
Reviewed-by: Michael Meeks <michael.meeks@suse.com>
Tested-by: Michael Meeks <michael.meeks@suse.com>
Diffstat (limited to 'test/README')
| -rw-r--r-- | test/README | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/test/README b/test/README new file mode 100644 index 000000000000..401f5d7e95f2 --- /dev/null +++ b/test/README @@ -0,0 +1,6 @@ +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:
+workdir/unxlngx6/JunitTest/<module>_complex/done.log
+The log file will contain a Java stack trace of the failed test
\ No newline at end of file |