[Ocfstest-commits] colinzhu commits r26 - trunk/Docs

[svn-commits at oss.oracle.com]

Author: colinzhu
Date: 2005-04-13 08:43:43 -0500 (Wed, 13 Apr 2005)
New Revision: 26

Added:
   trunk/Docs/README.quickstart
Log:

Quick start file added



Added: trunk/Docs/README.quickstart
===================================================================
--- trunk/Docs/README.quickstart	2005-04-13 07:02:50 UTC (rev 25)
+++ trunk/Docs/README.quickstart	2005-04-13 13:43:43 UTC (rev 26)
@@ -0,0 +1,50 @@
+		Quick Start for automatic ocfs2 testing kits
+
+Steps to build and run current test cases:
+
+1, Fetch source from oss.oracle.com via svn:
+
+[root at node2 opt]# svn checkout http://oss.oracle.com/projects/ocfstest/src/trunk/  /opt/ocfs2test
+
+2, Enter ocfs2test bin directory and do configuration work (finish all the "make" needed and build some other files needed)
+
+[root at node2 opt]# cd /opt/ocfs2test/bin
+[root at node2 bin]# ls
+config_ocfs2.sh  test_ocfs2.sh
+[root at node2 bin]#  ./config_ocfs2.sh
+
+And it will build all the source need to be made. And brought the contents of the configuration file to your screen (which locates at </opt/ocfs2test>/ocfs2test/src/TestSuites/ocfs2test/tset/testenv.sh). Modify the settings in this file to be suitable for your environment if you need.
+
+3, Still in the bin directory, start the automatic testing:
+
+[root at node2 bin]#  ./test_ocfs2.sh
+
+And wait for some time until all the cases are done.
+
+4, After all the cases done, report for all the cases will be displayed on screen. But you can still find it at </opt/ocfs2test>/ocfs2test/src/TestSuites/ocfs2test/tset/log if you missed screen output.
+
+Tips:
+Opening another terminal window and monitor system with "tail -f /var/log/messages" is a good way to learn what happens in system now. (Congratulations if you saw any "Call Trace" or Oops.......  :D )
+
+Comments:
+1, All the testing cases are running in a way that it generated some results by operations in current environment (all the individual system specified info are tried to filtered, just common info left) and compare these results with standard result files. So if in future version standard output by ocfs2/tools are changed, related standard result files also need to be re-made.
+
+2, Current standard result files are based on ocfs2 svn 2097 and ocfs2tools svn 767
+
+3, Case B2 (mkfs.ocfs2) may fail for ocfs2tools svn versions later than svn 792 since after that mkfs.ocfs2 changed a lot. (Please make a new rpm for us to build a new standard result.  :) )
+
+4, Case B4 should be more meaningful if we run some data corruption simulations before.
+
+5, In case B7, if we change the parameters of the width and level numbers of the deep directory tree to large numbers. This case may crash with "Segmentation Fault" errors.
+
+6, The standard result file for case B9 is an error message in fact, since mmap() functions are not implemented totally in current ocfs2 build yet.
+
+7, Case B11 is blank since no ioctl() call implemented. (Any updates recently?)
+
+8, The result for case B14 is different with the expected results in test plan.
+
+9, The result for case B17 is different with the expected results in test plan.
+
+10, The result for case B19 is different with the expected results in test plan.
+
+