Versions Compared

Old Version 125

changes.mady.by.user Scott Amerson

Saved on

compared with

New Version 126

changes.mady.by.user Scott Amerson

Saved on

Key

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

...

Tip
titlePurpose for this testing

The purpose of this test plan is to regression test the provider functionality, which in SmartSite includes:

UserDirectoryProvider

  1. Support for WebDav authentication (via Kerberos)
  2. Provide user account information (e.g. first,last,email,type) from outside data source (e.g. feed from Mothra)

GroupProvider

  1. Assign roles to users who log in to SmartSite that correspond to Sakai internal roles (e.g. Student, Instructor) when applicable. These roles need to be queried from an external data source (e.g. Banner mViews), so that authorization can be determined in real-time.
  2. Define the sites a user belongs to when they log into SmartSite.

CourseManagementProvider

  1. Retrieve dynamic rosters for courses, including updates within specific time interval. Roster updates from Banner need to be displayed in the SmartSite application within a pre-determined acceptable time period as defined by the user acceptance testing group.
  2. Display current instructor(s) course sites and display them as members in the course with appropriate role
  3. Display Banner course details in the SmartSite UIDisplay site membership changes in a course site, including instructor adds/removals/updates

...

  • Realms not refreshing frequent enough
  • Rosters not accurate with Banner
  • Drops not showing in SmartSite UI
  • Known (not fixed) issue #1 for Resources tool (e.g. using WebDav), is that when a file is uploaded to the system, metadata is written to the database before the file is stored on the file system. This is a feature of Sakai, which was detected during some resource discussion re:AFS file storage. For this reason, a resource may "seem" to be updated correctly, and listed in the resouce tool however the content cannot be seen. An http 404 error is thrown (No page can be found). This error is NOT fixed for this testing, just a known issue for Case 1a.
  • Known (not fixed) issue #2 is that whatever user that creates the sites when logged in is placed as a member in the site. Therefore, if ssbatchadmin created sites then the roster for such sites may appear off by 1.
  • Known (not fixed) issue #3 is that the instructor presented in the member list is not presented first. This is a default sorting behavior within SmartSite and will not be fixed.

...

Info

*NOTE: The order of the test cases will be as follows.

Setup Case (0a): Accessing server
Setup Case (0b): Login access via DistAuth
Setup Case (0c): Login outside of DistAuth (e.g. internal account)
Setup Case (0d): Accessing admin functionality

Case 1: User Directory Provider
1a) Web Dav authentication
1b) User directory lookup functionality

Case 2: Group Provider
2a) Roles in courses verified by tabs
(1) Roles in courses verified by system log output (system admins)
2b) Realm refresh via browser refresh button
(1) Realm refresh seen in system log output (system admins)

Case 3: Course Management Provider
3a) Rosters from Banner viewed by instructor and administrator role in site
3b) Adds/drops of students from Banner seen in SmartSite UI
3c) Roster details accurate (e.g. kname, role, etc)
3d) Instructor changes for a course seen in participants list for a site
3e) Course Site information viewed by instructor seen in site summary details

TEST CASES

Info
titleKey for Test Case Scenarios

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

...