Versions Compared

Key

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

...

Note
titleWhite List Testing

Description = Test the capability of the system to add "on-demand" course sites that are listed in a file. Courses are not required to have any enrollment in order to be created.

Category of Testing = unit, integration

Prerequisite Steps

  1. Scott will add a list of CRNs (valid or not) as the white-list.txt file in /var/sakai/ucd-data folder on the server, in the form of TERMYR-TERMCD-CRN for each entry. Use this file file to use here
  2. Scott will que the batch job to run, only for the above list (5 min elapsed time needed)
  3. Scott will give maintain permissions on the applicable sites, to the appropriate users
  • Brian = look up CRN xxxxx
  • Sandra = look up CRN yyyyy
  • Scott will assist users in accessing the site(s) if needed
  • Thomas = view logs, look up CRN zzzzz
  • James Jon G. = look up CRN wwwww
  1. Scott will advise programmers that the batch has been run and sites have been created
  2. Thomas and Scott will monitor server activity while testers are using sakai-dev.

Test Scenario

  1. Above users will perform functionality testing for each CRN, including :
    **perform functionality test https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/Course+Site+Functionality+Tests%2C+SmartSite+Batch+Integration+Testing+Matrix for each site
    **perform course management test https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/SmartSite+Course+Site%2C+Course+Management+Integration+Test+Matrix for each site
    **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

Test Cleanup

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

...

Info
borderColor#ccc
bgColorefefef
titleBGColorffffcc
titleTest Results, White List
borderStyledashed

Test

User Role

User Acting As

Result

Expected Result

Pass/Fail

Site xxxxx (created): Functionality Results

bdonnell

Test

User Role

User Acting As

Result

Expected Result

Pass/Fail

Site yyyyy (created): Functionality Results

smavocet

Test

User Role

User Acting As

Result

Expected Result

Pass/Fail

Site wwwww (created): Functionality Results

tpamsler

Test

User Role

User Acting As

Result

Expected Result

Pass/Fail

Site zzzzz (created): Functionality Results

jrenfroccjon

Black List

Note
titleBlack List Testing

Description = Test the capability of the system to not add course sites that are listed in a file. Courses in this list will never be batch created.

Category of Testing = unit, integration

Prerequisite Steps

  1. Scott will add a list of CRNs (valid or not) to the white-list.txt file in /var/sakai/ucd-data folder on the server, in the form of TERMYR-TERMCD-CRN for each entry. This list will be different than that used for the White List Test Scenario. Use this white list
  2. Scott will add a list of CRNs (valid or not) to the black-list.txt file in /var/sakai/ucd-data folder on the server, in the form of TERMYR-TERMCD-CRN for each entry. Use this black list file file to use here
  3. Scott will que the batch jobs to run, first Black List, then White List, (5 min time elapse needed)
  4. Scott will advise programmers that the batches have been run
  5. Thomas and Scott will monitor server activity while testers are using sakai-dev.

Test Scenario

  • Jon G. = will look for CRN xxxxx, yyyyy, zzzzz as user ....... These CRNs will be listed in the Black List
  • Brian = will look for CRN aaaaa that is listed both in the white-list.txt and black-list.txt files
  • Thomas = view logs, internal sakai db
  • Scott = help Jon

Test Cleanup

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

...

Note
titleUpdate existing sites with appropriate provider id, enabling dynamic rosters (**if CourseMgmtProvider 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 StepsTest Scenario

  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
  • Sandra = will look for site yyyyy's providerid and roster
  • Brian = will validate provider ids and rosters
  • Thomas = view logs, internal sakai db
  • Scott = help Sandra, Jon

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

  1. After site xxxxx and site yyyyy's provider ids are validated,
    Scott will update site xxxxx with:
    providerId =
    and.. site yyyyy with:
    providerId =

Test Cleanup

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

...