...
- Hardware Setup
Server Type
Location
database
bricker.ucdavis.edu with banner-test (external db), and sakai dev test (internal db)
application
isaac.ucdavis.edu, sakai-devtest
web server
url,
http://sakai-devtest.ucdavis.edu
- Note: The application does not need to be stopped for these tests to occur
...
- Additional Setup Needed
**Batch admin account (e.g. ssbatchadmin)
**QA admin account (e.g. QAadmin)
**Programmers Testers have access to testable sites (via SU tool, admin workspace)
**SU tool and Quartz tools are available in admin workspace/realm
**All login accounts that reference kerberos names can be "provided"
...
- At least UserDirectoryProvider enabled to allow user accounts to be looked up automatically via kerberos name (Note:all Providers will be enabled)
- Distributed authentication using AFS (SAK-143)
- Sakai-dev will be used in its current statetest database will be a copy of existing production data, so sakai-test will have to be backed up prior to testing
- We will be referencing sakai-test external for populating course data
ROLES AND RESPONSIBILITIES
- Unit/Integration Testers (ProgrammersQA, Managers, students etc)*
- which would include any Admins and SmartSite Programmers
- Any of the following persons that may be available:
Application admins (Programmers available, including Thomas, Lisa W., James, Brian, Jon G., Scott)
Database mViews admin (Brian Donnelly)
- Any of the following persons that may be available:
...
- /system admins (Geeta, Chris Callahan)
All of the above users will have access to the admin realm in Sakai, in addition to:
ssbatchadmin
QAadmin
COURSE SITE BATCHING DOCUMENTATION
...