Update testsuite README

test/testsuite/README

@@ -77,7 +77,7 @@ Configuration for running the APF spec tests
 - 2 users: <user1> <user2> with the same password
 - 3 group: <gp1> <gp2> <common>
 - with gp1:user1, gp2:user2, common:user1, user2
-- clear text UAM
+- clear text UAM + guest UAM
 - an empty volume:
 drwxrwsr-x    5 user1   common         176 avr 27 23:56 test/
 - some tests need a small read write volume, I'm using a 2 MBytes loopback
@@ -89,10 +89,14 @@ afp.conf:
 uam list = uams_clrtxt.so uams_guest.so
 
 [test1]
+appledouble = ea
 path = /tmp/afptest1
+valid users = @afpusers
 
 [test2]
+appledouble = ea
 path = /tmp/afptest2
+valid users = @afpusers
 #<<<<<<<<
 
 For testing with a Mac, same config (user1 or user2 are not owner)
@@ -113,20 +117,20 @@ Return Codes
 2 NOT TESTED - a test setup step or precondition check failed
 3 SKIPPED - test environment requirements not satisfied
 
-Note that 2 and 3 are treated as an overall return code 0 for the purpose of test reporting.
+Note that 3 is treated as an overall return code 0 for the purpose of test reporting.
 
-spectest, logintext and rotest shall return the same results whether they are run
+spectest tier 1, readonly, and logintest shall return the same results whether they are run
 on a Mac server or afpd.
 
 Example:
 --------
 Run all tier 1 spec tests on server 192.168.2.123
-afp_spectest -F tier1 -h 192.168.2.123 -u user1 -d usr2 -s test -w toto
+afp_spectest -F tier1 -h 192.168.2.123 -u user1 -d user2 -s test -w toto
 Same but on a Mac
 afp_spectest -F tier1 -m -h 192.168.2.64 -u user1 -d usr2 -s test -w toto
 
-Run FPByteRangeLock tests with AFP 3.0, two different servers are exporting the same volume.
-afp_spectest -f FPByteRangeLock -3 -h 192.168.2.123 -H 192.168.2.124 -u user1 -d usr2 -s test -c /tmp/afptest1 -w toto
+Run tier 2 FPByteRangeLock tests with AFP 3.0, two different servers are exporting the same volume.
+afp_spectest -f T2FPByteRangeLock_test -3 -h 192.168.2.123 -H 192.168.2.124 -u user1 -d user2 -s test -c /tmp/afptest1 -w toto
 
 At least on linux, it's possible to compile them with LDFLAGS=-rdynamic
 and the program can run individual test:
@@ -154,4 +158,4 @@ List tests
 One way to get a list of tests that are actually implemented,
 is to grep for symbols in the compiled binaries.
 
-nm afp_logintest afp_ls afp_spectest | cut -d " " -f 3 | egrep "^test[[:digit:]]+" | sort -n -k 1.5
+nm afp_logintest afp_spectest | cut -d " " -f 3 | egrep "^test[[:digit:]]+" | sort -n -k 1.5