generic: new case to test getcwd(2)

[xfstests-dev.git] / README

diff --git a/README b/README
index 2d231de2c22be76d6b42a7e3bf15a50d25afae33..b299c8fc783d5996ddff8b8bb76e84f1b405da91 100644 (file)
--- a/README
+++ b/README
@@ -65,7 +65,15 @@ Preparing system for tests (IRIX and Linux):
                environment variable set to "yes" will enable their use.
              - setenv DIFF_LENGTH "number of diff lines to print from a failed test",
                by default 10, set to 0 to print the full diff
-        - or add a case to the switch in common.config assigning
+             - setenv FSTYP "the filesystem you want to test", the filesystem
+               type is devised from the TEST_DEV device, but you may want to
+               override it; if unset, the default is 'xfs'
+             - setenv FSSTRESS_AVOID and/or FSX_AVOID, which contain options
+               added to the end of fsstresss and fsx invocations, respectively,
+               in case you wish to exclude certain operational modes from these
+               tests.
+
+        - or add a case to the switch in common/config assigning
           these variables based on the hostname of your test
           machine
        - or add these variables to a file called local.config and keep that
@@ -81,9 +89,11 @@ Running tests:
 
     - cd xfstests
     - By default the tests suite will run xfs tests:
-    - ./check 001 002 003 ... or you can explicitly run a filesystem: 
-      ./check -xfs [test(s)]
-    - You can run a range of tests: ./check 067-078
+    - ./check '*/001' '*/002' '*/003'
+    - ./check '*/06?'
+    - You can explicitly specify NFS, otherwise the filesystem type will be
+      autodetected from $TEST_DEV:
+      ./check -nfs [test(s)]
     - Groups of tests maybe ran by: ./check -g [group(s)]
       See the 'group' file for details on groups
     - for udf tests: ./check -udf [test(s)]
@@ -113,7 +123,7 @@ Test script environment:
 
     When developing a new test script keep the following things in
     mind.  All of the environment variables and shell procedures are
-    available to the script once the "common.rc" file has been
+    available to the script once the "common/rc" file has been
     sourced.
 
      1. The tests are run from an arbitrary directory.  If you want to
@@ -166,7 +176,7 @@ Test script environment:
        _within_tolerance       - fancy numerical "close enough is good
                                  enough" filter for deterministic
                                  output ... see comments in
-                                 common.filter for an explanation
+                                 common/filter for an explanation
 
        _filter_date            - turn ctime(3) format dates into the
                                  string DATE for deterministic
@@ -203,9 +213,6 @@ Verified output:
     - variable directory contents
     - imprecise numbers, especially sizes and times
 
-    Use the "remake" script to recreate the verified output for one
-    or more tests.
-
 Pass/failure:
 
     The script "check" may be used to run one or more tests.