STP Rollout - Basic Order
1. Stop the STP queue
2. Do final database conversion
3. Update PLM RPM's and verify installation 
4. Update STP RPM's and verify installation
     - systemimager master files ( version change )
     - proper db name and db user password in cfengine
     - proper install of new /etc/stp configuration files
5. Redirect Zope to the new interface
6. Restart the queue.
7. Verify installation of new reporting scripts


INITIAL TESTING
1. run and observe -
- DBT* test ( ask markw for help )
- reaim 
- iozone.
- verify proper operation of test, proper display of results

2. Search previous results ( basic web form )
- verify that old test reports are still reachable
- verify that compressed and un-compressed files are opened correctly.
- verify that graphs, .png files are displayed properly
3. test data_mining 
- .....somehow....
4. Run bad kernels.
- re-verify failure conditions under production use.

----------------------------------------------

STP Rollout - Ops Issue List
1. Zope - Ken and Bryce
             - under control

2. STP RPM - Cliffw
            - testing proceeds, results good so far

3. Database Conversion - Judith
           - Ops test install ?

4. PLM Upgrade - Judith

---------------------------------------------

STP 3.0 Test Plan
FREQUENTLY ( daily if possible )
CL004 - 
	1. Dump production database
	2. Create new STP database instance and
		migrate production data to it
	3. Validate migration and data quality
	4. Install latest STP RPM
	5. Run schedule of tests
Testdev2-002

	1. Validate Zope bits 
	2. Update of Zope depends of Ops release of
		newer bits

	3. PLM DB instance should be static ?

1. Engine
   A. Basic Operation
      1. Audit of Maint Exits - DONE w/kees
      2. Test Runs - proper results uploaded - DONE
      3. Test Failed - proper upload - DONE
      4. Kernel Build Failed - proper upload - DONE
      5. Package Build Failed - proper upload
   B. Test Parameters
      1. Parameters properly passed to wrap.sh - DONE
      2. Check for bad params, or assume web will catch?   
   C. Multiple Stack
      1. Test sysstat added to stack - DONE
      2. Test PostgreSQL added to stack
   D. Sysctl
6/2004

1. Stp_cron.pl
	1. Schedule single test on available machine - DONE
	2. Schedule multiple tests on multiple machine - DONE
	3. Schedule different priority tests in proper priority order
	4. Detects maint state when needed
	5. Does not set maint state unless needed
	6. If possible, force every error exit and check resulting
		output. 
             TESTING 7/19 - Timeout in state inst - FIXED
                          - Test timeout in state compile - DONE
                          - Test timeout in state reboot - DONE
                          - Test timeout in state runtest - DONE
                          - Test timeout in state upload  - DONE

2. stp_client.pl

	1. test runing simple test - DONE
	2. test w/multiple packages - DONE
	3. verify sysstat install scripts - DONE 
	4. fix utils so sysstat PLM is detected
	5. test reboot on demand ( create new dummy_test )
	6. test filesystem creation
	7. test proper parameter input to script - DONE
	8. test proper parameter upload to DB - DONE
	9. test result set upload to DB
	10. test sysctl operation ( params from markw )
              TESTING 7/19 - Error exit conditions
                     - System reboots in state 'avail' - DONE
                     - System reboots in state 'compile' - DONE
                     - System reboots in state 'running test' - DONE
                     - System reboots in state 'upload' - DONE
  

2. Web Interface
   A. Test Entry
      - Inset List of tests, including-
	      - multiple params
	      - no params
	      - multiple PLM's 
       - Attempt to insert *bad* data
	 - bad PLM
	 - bad param
	 - Other?
   B. User Page
     - Verify Content is correct
     - Verify with at least two outside users ( outside testdev team )
   C. Test Search
      - Verify wildcards work
6/2004	1. Requires login for test request & userpage, not for search
        2. Navigation & usability as a whole
        3. Static pages - usefulness / clarity?
           - Overview
           - Guide
           - How to Config Kernel
           - How to Port Tests
           - Script Parameters
           - What other docs are missing
        4. Test request forms (5 pages)
           - Basic functionality
           - Clarity / documentation
           - Error conditions / data validation
           - General look & feel
           - Test options (known bugs for some cases)
        5. Userpage
        6. Search page
           - Layout / clarity / look & feel of search form
           - Is the set of info displayed in search results table useful?
           - View test info functionality - (i) button
           - Cancel test functionality - (x) button


3. Data Mining
   1. Installation
   2. Queries - Examine SQL Output, and then run query.
       a. Basic
       b. 'OUTER JOIN' Queries
           1. Queries with parameters
           2. Queries with result sets
           3. Queries with both parameters and result sets
       c.  Tests with the different types of parameters
           1. switch
           2. pair
           3. value
   3. Saving Results sets
   4. Recalling Results sets
   5. Graphing of result sets vmstat
   6. Check that user cannot do UPDATE (expept for result_set)
   7. Result set compares.

4. Installation and Ops
   1. Database conversion
   2. Database re-install 
   3. Zope installation 
   4. Operations documentation audit

5. PLM
   1. Test plm database updates script on new version of database.
        *  Run plm_build_tree.pl, plm_build_app.pl on linux,
               sysstat, postgress.
        *  Add patch, reverse_patch
   2. Check that all configuration changes are documented for
       STP, supervisors, server