/
SmartSite Provider QA Test Plan

SmartSite Provider QA Test Plan

Sept 20, 2006

TEST PLAN DATE

Testing date:

TEST PLAN OVERVIEW

Scope of testing

This document is designed to guide Quality Assurance in the functionality testing of the provider mechanisms within SmartSite. The functionality of the provider mechanisms, as detailed by the given test cases in this plan, are driven by the functional requirements at :http://confluence.ucdavis.edu:8080/confluence/display/UCDSAKAI/Sakai+Providers.

Additionally, the level of involvement by QA, system administrators, and programmers will be detailed for each test case.

Purpose 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 site membership changes in a course site, including instructor adds/removals/updates

KNOWN ISSUES / PREVIOUS BUGS FIXED

Previously determined bugs have been fixed for this testing, they were identified as the following. They are also summarized in the table of Jiras referenced in this test plan.

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

  • Known (not fixed) issue #4 http://jira.ucdavis.edu:8080/jira/browse/SAK-202 is that the instructor presented in the member list may be still listed even if they have been "replaced"

JIRAs that explain features and past bugs fixed, to be tested in this plan

Summary of the Jiras related to this test plan, which have been fixed:
BATCH TESTING BUGS FIXED:http://jira.ucdavis.edu:8080/jira/browse/SAK-184 (1000 row limit on associations (realms) for sakai internal query)
BATCH TESTING BUGS FIXED:http://jira.ucdavis.edu:8080/jira/browse/SAK-185 (term abbreviation and term description do not match in site information tool)
PREVIOUS PROVIDER TESTING BUGS FIXED:http://jira.ucdavis.edu:8080/jira/browse/SAK-197 Support and Training web link should be present, going to gateway site on sakai2
PREVIOUS PROVIDER TESTING BUGS FIXED:http://jira.ucdavis.edu:8080/jira/browse/SAK-201 authz group refresh interfering with batching of courses, noticed in provider integration testing
PREVIOUS PROVIDER TESTING BUGS FIXED:http://jira.ucdavis.edu:8080/jira/browse/SAK-124 (Banner rosters not in sync with SmartSite UI)
PREVIOUS PROVIDER TESTING BUGS FIXED:http://jira.ucdavis.edu:8080/jira/browse/SAK-125 (drop student from Banner and not reflected in SmartSite UI)
PREVIOUS PROVIDER TESTING BUGS FIXED:http://jira.ucdavis.edu:8080/jira/browse/SAK-132 (realms not refreshing fast enough in the providers)

JIRAs that reference test scenarios, "QA Tests" described in this test plan

http://jira.ucdavis.edu:8080/jira/browse/SAK-155 When users log into Sakai, their user information is looked up externally in Mothra, LDAP, or some other central datasource for campus
http://jira.ucdavis.edu:8080/jira/browse/SAK-156 User logs into Sakai, and sees the tabs associated with their enrollment (roles) in courses from Banner, as well as sites internally defined in Sakai (e.g. projects)
http://jira.ucdavis.edu:8080/jira/browse/SAK-157 Course information must be pulled dynamically from Banner, within Sakai
http://jira.ucdavis.edu:8080/jira/browse/SAK-154 User is able to used WebDav in Sakai, with their Kerberos username and password

TEST ENVIRONMENT

  • Hardware Setup

INTEGRATION TESTING

SETUP

Server Type

Location

database

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

application

hanley.ucdavis.edu, sakai-dev

web server

url,

https://hanley.ucdavis.edu:8443/portal

population of data referenced

2006 Fall Quarter Banner Test data (external), and clean sakai internal database with exception of necessary login accounts and manual sites created)

QA TESTING

SETUP

Server Type

Location

database

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

application

isaac.ucdavis.edu, sakai-test

web server

url,

http://sakai-test.ucdavis.edu

population of data referenced

2006 Fall Quarter Banner Test data (external), and clean sakai internal database with exception of necessary login accounts and manual sites created)

Comments