Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 state
  • We will be referencing sakai-test external for populating course data

...

Note
titleUpdate existing sites with appropriate provider id, enabling dynamic rosters (**When CourseManagementProvider enabled**)

Description = Test the capability of the system to update existing course sites with associated provider ids. This functionality can be done either in the UI or batch, however we want to
test the ability to run this at any time.

Category of Testing = unit, integration

Prerequisite Steps
Results Recording Steps summarized in:
**perform provider id test https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/SmartSite+Provider+Id+Update+of+Existing+Sites%2C+Integration+Test+Matrix for each site

  1. Scott will add a list of sites and provider ids (valid or not) to the provider-list.txt file in /var/sakai/ucd-data folder on the server, in the form of site id, TERMYR-TERMCD-CRN for each entry. Use this file use file here
  2. Scott will que the batch jobs to run, just the provider id que batch run, (5 min time elapse needed)
  3. Scott will advise programmers that the batch has been run
  4. Thomas and Scott will monitor server activity while testers are using sakai-dev.

Test Scenario

  • Jon G. = will look for site xxxxx's providerid and roster, logging in as admin
  • Sandra = will look for site yyyyy's providerid and roster, logging in as ssbatchadmin
  • Sandra = will look for site zzzzz's providerid and roster, logging in as ssbatchadmin
  • Brian = will validate provider ids and rosters
  • Thomas = view logs, internal sakai db
  • Scott = help Sandra, Jon, and log in as himself for manual updates

Manual Process Check (update provider ids for sites manually):

  1. After site xxxxx,yyyyy, and zzzzz's provider ids are validated,
    Scott will update site xxxxx with:
    providerId =
    and.. site yyyyy with:
    providerId =
  2. Thomas will check site xxxxx and site yyyyy's provider id and rosters

Test Cleanup

  1. Scott will remove all sites created in this step when all test cases are completed.

...

Results Recording Steps summarized in:
**perform functionality test https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/Course+Site+Functionality+Tests%2C+SmartSite+Batch+Integration+Testing+Matrix for each site

Test Scenario

Note
titleSite functionality

Description = Test the capability of the system to add sites with the correct pages, tools, tabs, and look and feel.

Category of Testing = unit, integration, functionality

Prerequisite Steps

Test Scenario

Panel
Panel
borderColor#ccc
bgColorF7D6C1
titleBGColor#efefef
titleIndividual Functionality Tests
borderStyledashed
  • -Look and Feel- *
  • Pages *
  • Tools on each page *
  • Click-through on tools *
  • Order *
  • Tabs *

Test Cleanup

  1. Scott will remove all sites created in this step when all test cases are completed.

...

Note
titleCourse Management data present

Description = Test the course management content displayed in admin tools.

Category of Testing = unit, integration, functionality

Prerequisite Steps
Results Recording Steps summarized in:
**perform course management test https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/SmartSite+Course+Site%2C+Course+Management+Integration+Test+Matrix for each site

Panel
borderColor#ccc
bgColorwhite
titleBGColorefefef
titleTest Scenario
borderStyledashed
  • Site navigation *
  • WorkSite Setup navigation *
  • Site Info tool *

Test Cleanup

  1. Scott will remove all sites created in this step when all test cases are completed.

...