Versions Compared

Old Version 138

changes.mady.by.user Scott Amerson

Saved on

compared with

New Version 139

changes.mady.by.user Scott Amerson

Saved on

Key

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

...

Note
titleCase 2b, Realms refresh test

Description = Test the capability of the AuthxGroups to be updated more frequently than default OOTB

Category of Testing = functionality,regression

Prerequisite Steps

  1. Site user is a member of must be already created prior to test (via Batch? via manually?)
  2. User must be a member of the sites in order to see the tab
  3. If user is an externally provided one, then they must be in either the external database (Banner) or already in the internal SmartSite database

Test Scenario 2b, Realms refreshing

  1. Staying as user from Case 2a, record the site tab that is highlighted
  2. Brian Donnelly will add a user to this given site, through the external db (by adding a user this way, the 15 minute refresh doesn't have to occur to see the end results)
  3. Scott will notify Pat Kava of what user has been added to the course externally
  4. Pat will verify that by hitting the browser refresh after 5 minutes elapsed since update, that the user added appears as a member in the site

Additional step for programmers (Case 2bi), verify that authz refresh is happening via the log output, and at what intervals

  • Data to Be Used:
    QA determines

Test Cleanup
None

...

Note
titleCase 3b, Roster Update Tests (student add(1), student drop(2))

Description = Test the capability of the CourseMangementProvider to accurately reflect within the SmartSite UI, students added to a Banner roster within an alotted time period

Category of Testing = functionality,regression

Prerequisite Steps
*Current roster given or available to QA for respective courses to be tested
*Courses with test CRN's are created either by batch list or full batch mode

Info
titleCase 3b(1), Roster add

Test Scenario 3b(1), Roster Add

  1. Coordinator will talk to Libby about adding:
    student pidm (2204701), kerberos name kdas to CRN (2006-10-)28142
    student pidm (163004),kerberos name larivers to CRN (2006-10-)28142
    student pidm (163004),kerberos name larivers to CRN (2006-10-)26423
  2. Record times when updates start, and when they are finished
  3. Wait until external db refresh happens, based on recorded time(s)
  4. Coordinator will advise testers when update has occured
  5. Log in as instructor for one of these courses, and click Site Info to view updated roster adds above

Description = Test the capability of the CourseMangementProvider to accurately reflect within the SmartSite UI, students dropped from a Banner roster within an alotted time period

Category of Testing = functionality,regression

Prerequisite Steps
Current roster given to QA for respective courses to be tested

Info
titleCase 3b(2), Roster remove

Test Scenario 3b(2), Roster Delete

  1. Coordinator will talk to Libby about adding:
    student pidm (1107630), kerberos name dclu dropped from CRN (2006-10-)13185
    student pidm (2218507), kerberos name djf27 dropped from CRN (2006-10-)32457
  2. Record times when updates start, and when they are finished
  3. Wait until external db refresh happens, based on recorded time(s)
  4. Coordinator will advise testers when update has occured
  5. Log in as instructor for one of these courses, and click Site Info to view updated roster deletes above
  6. Log in as kerberos names above, see if any 2006 Fall tabs show up
  • Data to Be Used:
    QA determines if there are additional updates from list of available sites above.

Test Cleanup
None

...