Course Batch Creation Test Plan, Unit and Integration Testing

The automatic course creation mechanism for SmartSite. Course sites, when done automatically via chron jobs, can be created and/or updated in several ways

1. On-Demand List of courses (White list)
   • Will create only a pre-defined list of course sites
   • Not specific to a Term
2. Excluded List of courses (Black list)
   • Will not be created by any mechanism
3. Auto-update of existing course sites with group update (e.g. provider id)
   • Sets existing sites with the assigned provider id value, and will not provision a duplicate site with same provider id from full other batch run
4. Full run of course creation for a designated term (will not batch white or black lists, as well as not create sites with Provider Id to be set)

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
• 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

• 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

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.

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

• 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
• Sandra = will look for both CRN bbbbb, ccccc that are listed both in the white-list.txt and black-list.txt files
• Thomas = view logs, internal sakai db
• Scott = help Jon
• 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	White 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	White List	white-list.txt
  CRN with enrollment	2006-01-40018	14 (all valid knames)	calymos (Calvin Lymos)	AAS, 154, 001, University Gospel Choir	Winter Quarter 2006	White List	white-list.txt,black-list.txt

  TODO, add more blacklisted here

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

• 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 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	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	White 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	White List	white-list.txt
  CRN with enrollment	2006-01-40018	14 (all valid knames)	calymos (Calvin Lymos)	AAS, 154, 001, University Gospel Choir	Winter Quarter 2006	White List	white-list.txt,black-list.txt

  TODO, add more blacklisted here

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

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

Test Cleanup

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

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

Test Cleanup

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

Description = Test the batch method for a whole term

Category of Testing = unit, integration, performance

Prerequisite Steps

• After all tests have been run, Scott will recompile the Batch code to run for 2004 Winter
• Scott will add the black list file that contains one CRN from Winter 2004 into the /var/sakai/ucd-data directory.
• This test will run in the evening of test day
• Scott and Thomas will analyze the Sakai internal db to check for errors in creation
• Data to Use:

  Scenario	Course	Roster Count	Instructor Kerb Name	Course Details (Catalog Root, Suffix, Section, Description)	Term Identifier	Test Case Used In	File Associated
  Valid Term
  Term with large number CRNs	2004-01	NA	NA	32573 sites	Winter Quarter 2004	Full Batch Run	NA
  Invalid CRN (Bogus Text)	2006-sfs-sfsfdfsdfsfsfs	NA	NA	NA	NA	White List	white-list.txt

  TODO|Valid CRN|2004-01-xxxxxx|NA|NA|NA|NA|White List|white-list.txt|

Test Cleanup

1. Scott will ask Geeta to drop the devel schema when this test is completed.