Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • Transfer all mothra ID changes to Banner schema.
  • Undo the temporary fixes wrt for CAS not using the MothraID but was using the Kerberos ID.
  • Sakai local.properties changes : rSmart's local.properties
    • Guest Access properties
      No Format
      guest.registration.tool.url=https://smartsite.ucdavis.edu/portal/site/f8382610-2f5b-4cd9-9687-564ca6e26b9c/page/41483e8f-08ae-4d89-9145-e50cdbb12fad?toolstate-1ed95b3d-c019-407b-88c6-0e657264d639=
      forgot.passwork.link=https://smartsite.ucdavis.edu/portal/site/f8382610-2f5b-4cd9-9687-564ca6e26b9c/page/41483e8f-08ae-4d89-9145-e50cdbb12fad?toolstate-1ed95b3d-c019-407b-88c6-0e657264d639=/register/pwreset
      
    • Gradbook 2 properties
      No Format
      final_grade_submission_url=https://classes.ucdavis.edu/CourseManagement/final_submit/fgs_direct_upload.cfm?sakai_id=
      final_grade_submission_enterprise_service_url=https://classes.ucdavis.edu/CourseManagement/final_submit/fgs_ss_deliver.cfm
      
      gb2.help.url=http://smartsite.ucdavis.edu:8000/smartsite/ucd-gateway/Gradebook2Documents.html
      
  • (warning) Make sure that rSmart configures their firewall to allow outgoing traffic to classes.ucdavis.edu
  • To make sure that the firewall is configured correctly, execute the following command:
    • No Format
      wget --no-check-certificate  https://classes.ucdavis.edu/CourseManagement/final_submit/fgs_ss_deliver.cfm
      
      # This should return something like the following. The key is  to get the "400 Bad Request" and not a 403
      
      
      Resolving classes.ucdavis.edu (classes.ucdavis.edu)... 128.120.33.73
      Connecting to classes.ucdavis.edu (classes.ucdavis.edu)|128.120.33.73|:443... connected.
      WARNING: cannot verify classes.ucdavis.edu¬タルs certificate, issued by ¬タワ/C=US/O=Equifax/OU=Equifax Secure Certificate Authority¬タ�:
        Unable to locally verify the issuer¬タルs authority.
      HTTP request sent, awaiting response... 400 Bad Request
      2009-12-16 14:44:03 ERROR 400: Bad Request.
      
    • CAS properties
      No Format
      login.url=https://smartsite.ucdavis.edu/xsl-portal/login
      loggedOutUrl=https://cas.ucdavis.edu/cas/logout?service=https://smartsite.ucdavis.edu/xsl-portal
      
    • CAS code changes
      No Format
      Change all the "smartsite-test.rsmart.com" references to "smartsite.ucdavis.edu in:
      https://svn.rsmart.com/svn/customizations/ucd/trunk/config/sakai-login-tool/rsmart.properties
      
      We probably need to create a new tag after the code changes.
      
    • Gateway URL references in local.properties
      No Format
      References to "http://smartsite-test.ucdavis.edu:8000/" need to be replaced with "http://smartsite.ucdavis.edu/ucd-gateway"
      

...

  • Bring up the system in maintenance mode
  • Verify that creating a new account sets the right tools and permissions in MyWorkspace
  • Verify all critical tools are present and functional (open, basic function, close) for project and course sites.
    NOTE: For items below do most of the testing on existing sites as creating new sites will send out emails
    • Test and Quizzes -- create a quiz.  Make sure students can take it.  Make sure instructor can see results.
    • Gradebook 2 -- Just make sure it's populated.
    • Section Info -- Make sure it creates automatically when you create a course site.  Make sure you can assign TAs (doe this as an Instructor not as an admin.)  Make sure that newly created course sites DO NOT have the Open Campus and Wait Listed Roles.
    • Site Info -- Make sure you can create and populate ad hoc  groups.  Make sure Site Info loads in 3-4 seconds.
    • Rosters -- Make sure you can see the Open Campus students in Enrollment Status.
    • Assignments -- Create an assignment, make sure the student can submit it, make sure the instructor can see the students work.
    • Web Content -- make sure you can create a link.
    • rWiki -- add a page
    • Announcements -- create an announcement.  Make sure participants can see it.
    • Chat -- create chat entries.  Make sure participants can see entries and create more.
    • Syllabus --
    • Mailtool -- send email to one of us.  Make sure we receive it.
    • Email Archive -- make sure mailtool et al copies to email archive.
    • Home -- Make sure it's there
    • Page Order tool -- Make sure it orders tools, renames, drops, adds.
  • Verify that we can create sites, project and course.
  • Verify that existing course and project sites have their same tools
  • Verify all known critical and blocker bugs have been fixed
  • Verify that OSP is fixed or not available for users.
  • Verify Guest Access:
    • add a guest, and verify email goes out to a real gues (e.g. test with real gmail accounts)
    • register as a guest,
    • activate a guest,
    • use the forgot your password function.
  • Verify that my campus messages works and doesn't require a second login.
  • Verify that the Support and Training link is present
  • Verify that project sites have the site statistics tool
    • Can Lead TAs use it?
    • Can Instructors use it?
  • Verify that all our tools are present for project and course sites and the defaults are checked.
  • Make sure that ad hoc groups works in old project sites.
  • Verify final grade submission url is point toward My Prod. [How is this done - need specific instructions here]
  • Verify Davis database markers can be found; internal database converted correctly
  • Verify the PDA portal works
  • Verify that the performance is 3 sec or better by running a load test. [a scripted load test or just visit Site info on large class??]
  • Verify that that all our roles exist:
    • new course sites can add Lead TA; 
    •  new project sites can add Organizer and Participant.  
    • Auditor,
  • Verify that the names of each server appears including the tag
  • Verify the gateway is correct - Kirk to make edits here above before QA starts as the one coming from UCD will be incorrect.]
  • Verify that MOTD works correctly
  • Verify response time is good
  • Verify Phoenix hot spare is being updated
  • Verify table create scripts are running as scheduled
  • Confirm Melete files exist and we can export a converted module
  • Verify SU (Super User) functionality in order to conduct intensive QA testing.

...