Versions Compared

Old Version 72

changes.mady.by.user Scott Amerson

Saved on

compared with

New Version 73

changes.mady.by.user Scott Amerson

Saved on

Key

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

...

  • Hardware Setup

    Server Type

    Location

    database

    bricker.ucdavis.edu with banner-test (external db), and sakai dev (internal db)

    application

    isaac.ucdavis.edu, sakai-dev

    web server

    url,

    http://sakai-dev.ucdavis.edu
  1. Note: The application does not need to be stopped for these tests to occur

...

  • External-Banner Test Data to be Used As Representative Course Scenarios

    Scenario

    Course

    Roster Count

    Instructor Kerb Name

    Course Details (Catalog Root, Suffix, Section, Description)

    Term Identifier

    Test Case Used In

    Invalid CRNs

    Invalid CRN (Number)

    20061-06-111

    NA

    NA

    NA

    NA

    White List, Provider Id

    Invalid CRN (Number)

    2006-06-12345

    NA

    NA

    NA

    NA

    White List

    Invalid CRN (Number)

    2006-03-60024

    NA

    NA

    NA

    NA

    White List

    *additional* Invalid CRN (Number) available

    1995-03-76288

    NA

    NA

    NA

    NA

    White List

    Invalid CRN (Bogus Text)

    2006-sfs-sfsfdfsdfsfsfs

    NA

    NA

    NA

    NA

    White List

    No CRN (empty file)

    null

    NA

    NA

    NA

    NA

    White List,Black List, Provider Id

    No CRN (null CRN value)

    null

    NA

    NA

    NA

    NA

    Provider Id

    Valid CRNs

    CRN with no enrollment

    1995-01-76288

    0

    fzthorn, (Robert Thornton)

    PLB, 092, 012, Internship

    Winter Quarter 1995

    White List

    CRN with no enrollment

    2004-03-60097

    0

    dlmiller (Douglas Miller)

    ECN, 298 , 026, Group Study

    Spring Quarter 2004

    Provider Id

    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,Black List,Provider Id

    CRN with enrollment

    2006-01-40018

    14 (all valid knames)

    calymos (Calvin Lymos)

    AAS, 154, 001, University Gospel Choir

    Winter Quarter 2006

    Black List

    CRN with large enrollment number

    2006-01-60001

    84 (all valid knames)

    ewlarsen (Eric Larsen)

    LDA, 190 , 001, ProSeminar

    Winter Quarter 2006

    White List

    TODO|CRN with large enrollment number|2006-03-xxxxx|NA|NA|NA|x|Provider Id|
    TODO|CRN with large enrollment number, some student kerbs don't exist|2006-03-xxxxx|NA|NA|NA|x|Provider Id|

    Valid Term

    Term with large number CRNs

    2004-01

    NA

    NA

    32573 sites

    Winter Quarter 2004

    Full Batch Run

  1. A few test course sites need to be created in advance so that the batch job can modify these sites with a respective provider Id. These sites are documented in the Provider Id Test Section.

DEPENDENCIES

  • 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
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. Note: The application does not need to be stopped for this test to occur
  2. 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
  3. Scott will que the batch job to run, only for the above list (5 min elapsed time needed)
  4. 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 = 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.

...

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

Note: The application does not need to be stopped for this test to occur

  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)
  1. Scott will advise programmers that the batches have been run
  2. 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.

...