Package Testing ProcessHere are my initial thoughts about standardizing testing of OACS packages:
Testing Servers - all testing is to be done on OACS testing servers found here: http://strauss.gast.it.uc3m.es/
Testing Platform - we are going to start testing the Postgres packages to start with. Testing for Oracle will be added depending on the outcome of the discussion on Oracle support.
- installation testing - does a package install cleanly
- automated testing - a request has been made to perform automated testing on all packages and create a short list of pass/fail values
- uninstall - does a package uninstall cleanly
- feature testing - test all features in a package and record breakage. We should look at using SELENIUM extrension for Firefox, it allows for recording of things you click on a page.
Packages Being Skipped - it has been mentioned that we should skip the testing of the .LRN packages, at least at first. Any comments on this?
Package Pages - right now we want to keep it simple, one page per package. It is all we need to get started. Each page will have the following items:
- Autogenerated - Package info at the top of the page
- Autogenerated - Bug list pulled in from bug tracker. Code for this is already created, will be submitted to CVS soon.
- Manual Editing - A simple table showing pass/fail for automated testing (step 2. of TESTING PROCESS)
- Manual Editing - Details about steps 1, 3, and 4 of the TESTING PROCESS.
- Robert Taylor (my self)
- Iuri Sampaio (thanks for the quick vote in previous thread!)
- Hamilton Chua - selenium programming and testing (thanks, this is very cool!)
- ... ??? ... sign up, you know you want to!
Any thoughts are welcome on these points, the general concensus seems to be, don't spend too much time over engineering the process but get some testing done.
More testing references: