src/afsweb/TestPlan.txt

   1 Copyright 2000, International Business Machines Corporation and others.
   2 All Rights Reserved.
   3
   4 This software has been released under the terms of the IBM Public
   5 License.  For details, see the LICENSE file in the top-level source
   6 directory or online at http://www.openafs.org/dl/license10.html
   7
   8 A very basic document describing some test ideas for AFS Web Secure (Apache)
   9
  10 1. HTTP tests
  11
  12         Ensure corect return codes (as per HTTP standards) are being reported for all methods (GET, HEAD, PUT, POST, etc.).
  13
  14 2. Authentication tests
  15
  16         Ensure ACL's and return codes match. ie. ensure that if the AFS acl
  17 permits access then the return code from the web server reflcts it and vice
  18 versa.
  19
  20 3. Cache consistency tests
  21
  22         Ensure that the token caches are updated and expiration times checked
  23 and expired tokens purged.
  24
  25 4. PAG tests
  26
  27         Ensure that each child process for the Apache Server has it's own PAG
  28 and authentication credentials for PAG's do not get mixed up.
  29
  30 5. CGI tests
  31
  32         Ensure that AFS acls permit or forbid CGI scripts executing.
  33
  34 6. Locking
  35
  36         Apache child processes use a shared pipe (synchromized by file locking)
  37 for inter process communication with the weblog process. This test would
  38 ensure that this communication is indeed synchronized and the request for
  39 an AFS token from one child process does indeed allow the token to be returned
  40 to that same child process with a unique PAG.
  41
  42 7. Performance testing
  43
  44         Memory leaks, speed.
  45
  46
  47 8. Propogate changes (release) from a read-write colume to read-only volumes
  48 and ensure the web server gives consistent file updates.
  49
  50