Page Comparison

*NOTE: The order of the test cases will be as follows.
White List Testing,
Black List Testing,
Provider Id Testing, and
Full Batch Run

1. Site Functionality Testing, Course Management Testing, and Provider Id testing are each part of the White List testing scenario.
2. In order to test the Black List functionality, we will need to have a superset of CRNs that are trying to be added at the same time. To accomplish this, we will use the White List scenario with a same CRN that is included in the Black List file. See Black List Test Scenario for more information.

Prerequisite Steps = actions needed before performing any of the given tests
Category of Testing = the described testing is at what level?
Description = description of the test performed

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 1995-01-76288
• Sandra = look up CRN 2006-06-60005
• Scott will assist users in accessing the site(s) if needed
• Thomas = view logs, look for CRN 20061-06-111, 2006-03-60024
• Jon G. = look up CRN 2006-sfs-sfsfdfsdfsfsfs

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

• Data to Be Used:

  Scenario	Course	Roster Count	Instructor Kerb Name	Course Details (Catalog Root, Suffix, Section, Description)	Term Identifier	Test Case Used In	File Associated
  Invalid CRNs
  Invalid CRN (Number)	20061-06-111	NA	NA	NA	NA	White List	white-list.txt
  Invalid CRN (Number)	2006-03-60024	NA	NA	NA	NA	White List	white-list.txt
  Invalid CRN (Bogus Text)	2006-sfs-sfsfdfsdfsfsfs	NA	NA	NA	NA	White List	white-list.txt
  *additional,not used for this testing* Invalid CRN (Number) available	1995-03-76288	NA	NA	NA	NA	White List	white-list.txt
  Valid CRNs
  CRN with no enrollment	1995-01-76288	0	fzthorn, (Robert Thornton)	PLB, 092, 012, Internship	Winter Quarter 1995	White List	white-list.txt
  CRN with enrollment	2006-06-60005	11 (all valid knames)	acham (Christine Acham)	AAS, 198, S01, Directed Gp Study	Summer Special Session 2006	White List	white-list.txt
  CRN with enrollment	2006-03-93307	10 (all valid knames)	fzvasili (S Spyridakis)	HIS 111C 001 Ancient History	Spring Quarter 2006	White List	white-list.txt,black-list.txt

Test Cleanup

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

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 job to run (White List), (5 min time elapse needed)
4. Scott will advise programmers that the batch has been run
5. Thomas and Scott will monitor server activity while testers are using sakai-dev.

Prerequisite Steps needed for Scenario #2 only (in addition to Scenario #1 steps)

1. Scott will update existing hand created sites manually (TBD site ids) with an associated CRN as the provider id

Test Scenarios
*Scenario #1 = Black list consulted when white list batch run is executed*

• James. = will look for CRN 2004-03-60097 as user admin. This CRN will be listed in the White List files only
• Brian = will look for CRN 2006-01-60001 that is listed both in the white-list.txt and black-list.txt files
• Sandra = will look for both CRN 2006-01-40018 that are listed both in the white-list.txt and black-list.txt files
• Thomas = view logs, internal sakai db, will look for both CRN 2006-03-82882, 2006-03-83634 that are listed in the black-list.txt files only
• Scott = help as needed
• Data to Be Used:

  Scenario	Course	Roster Count	Instructor Kerb Name	Course Details (Catalog Root, Suffix, Section, Description)	Term Identifier	Test Case Used In	File Associated
  Valid CRNs
  CRN with no enrollment	2004-03-60097	0	dlmiller (Douglas Miller)	ECN, 298 , 026, Group Study	Spring Quarter 2004	Black List	white-list.txt
  CRN with large enrollment number	2006-01-60001	84 (all valid knames)	ewlarsen (Eric Larsen)	LDA, 190 , 001, ProSeminar	Winter Quarter 2006	Black List	white-list.txt,black-list.txt
  CRN with enrollment	2006-01-40018	14 (all valid knames)	calymos (Calvin Lymos)	AAS, 154, 001, University Gospel Choir	Winter Quarter 2006	Black List	white-list.txt,black-list.txt
  CRN with enrollment	2006-03-82882	10	ltcmwc (Mark Connelly)	MSC 141 002 Army Mngmt Systems	Spring Quarter 2006	Black List	black-list.txt
  CRN with enrollment	2006-03-83634	10 (all valid knames)	eschang (Ernest Chang)	NPB 141P 001 Res In Physio Adapt	Spring Quarter 2006	Black List	black-list.txt

*Scenario #2 = Black list consulted when existing site already has provider id that matches black list entry*

• Jon G. = will look for CRN 2006-03-69857 as user ccjon. This CRN will be listed in the Black List, but have no existing site that has the provider ids matching the CRNs
• Brian = will look for CRN 2006-03-65306,2006-06-60435 that is listed both in the provider id reference for sites ^^^^^^^^, and (((((((( and black-list.txt file
• Thomas = view logs, internal sakai db
• Scott = help Jon
• Data to Be Used:

  Scenario	Course	Site id	Roster Count	Instructor Kerb Name	Course Details (Catalog Root, Suffix, Section, Description)	Term Identifier	Test Case Used In	File Associated
  Valid CRNs
  CRN with enrollment	2006-03-69857	10	jrlund (Jay Lund)	ECI 299 019 Research	Spring Quarter 2006	Black List	black-list.txt
  CRN with enrollment (large)	2006-03-65306	177 (all valid knames)	fzsegel (Leigh Segel)	BIS 103 002 Bioenergetics/Metabolism	Spring Quarter 2006	Black List	white-list.txt,black-list.txt
  CRN with no enrollment	2006-06-60435	0	fzblanch (Marc Blanchard)	COM 152 S01 Literature Of Americas	Summer Special Session 2006	Black List	white-list.txt,black-list.txt

Test Cleanup

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

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-id.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.

*Data To Be Used:

Test Scenario

• Jon G. = will look for site Scott's Test Course To Be Provided's providerid and roster, logging in as admin
• Sandra = will look for site A Second Course To Be updated By Batch's providerid and roster, logging in as ssbatchadmin
• James= will look for site Third Course Site Example's providerid and roster, logging in as admin (after Jon G. done)
• 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 Scott's Test Course To Be Provided,A Second Course To Be updated By Batch, and Third Course Site Example's provider ids are validated,
   Scott will update site Second Course Site Example with:
   providerId = 2006-03-76517
   and.. site Third Course Site Example with:
   providerId = 2006-03-75796
2. Thomas will check site Second Course Site Example and site Third Course Site Example's provider id and rosters

Test Cleanup

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

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
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
looking for expected results
Test Scenario