SmartSite Provider QA Test Plan

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.

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.

TEST ENVIRONMENT

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

1. Note: The application does not need to be stopped for these tests to occur

• Software Setup
  run test under https://mware.ucdavis.edu/svn/ucdsakai/branches/sakai-core-2.1.x branch, with mods from https://mware.ucdavis.edu/svn/ucdakai/sakai-core-2.1.x-scottsdev branch incorporated

• Additional Setup Needed
  **QA admin account (e.g. QAadmin)
  **All login accounts that use kerberos names can be "provided" by the system (e.g. UserDirectoryProvider implemented).
  **SU tool and Quartz tools are available in admin workspace/realm
  **Testers have access to testable sites (via SU tool, admin workspace, as user QAAdmin, etc.)
  **Run CourseManagement tests on existing batched sites perhaps? or run CourseManagementTests on new Fall Quarter Courses batched?
• mView refresh times must be recorded
• Additional External-Banner Test Data Used for Provider Testing
  A copy of test data that may be used for these test cases is attached: http://confluence.ucdavis.edu:8080/confluence/download/attachments/17096/200603TestData.xls

DEPENDENCIES

• All UCDavis Providers (UserDirectoryProvider, GroupProvider, and CourseManagementProvider) will be enabled to allow user accounts to be looked up automatically via kerberos name
• Distributed authentication using AFS should be enabled (SAK-143)
• Sakai-test database will be a copy of existing production data, so sakai-test will have to be backed up prior to testing
• We will be referencing sakai-test external for populating course data

ROLES AND RESPONSIBILITIES

• Testers (QA,students etc)*
• Admins and SmartSite Programmers
  • Any of the following persons that may be available:
    ***Application admins (Programmers available, including Thomas, Lisa W., James, Brian, Jon G., Scott)
    ***Database/system admins (Geeta Rayala, Chris Callahan)
    ***Banner admins (e.g. Libby Bullock)

*All of the above users will have access to the admin realm in Sakai, in addition to:
***QAadmin

PROVIDER DOCUMENTATION

• Requirements
  Provider requirements at: http://confluence.ucdavis.edu:8080/confluence/display/UCDSAKAI/UC+Davis+Data+Provisioning

• General Provider and Batching interaction documented at https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/Requirements+for+Data+Provisioning+using+Providers+and+Batch+Processes

• Functionality * http://confluence.ucdavis.edu:8080/confluence/display/UCDSAKAI/Sakai+Providers

UNIT AND INTEGRATION TEST RESULTS

Unit Test Results

The JUnit tests results that have been previously run on sakai-dev (isaac) are at:
http://confluence.ucdavis.edu:8080/confluence/display/UCDSAKAI/SmartSite+Provider+Unit+Test+Results%2C+run+Sep+11%2C+2006
In summary, all unit tests passed!!

Integration Test Results

TEST PLAN PROCESS

This SmartSite Provider QA Test Plan will be coordinated by Pat Kava, with assistance from the programming group (e.g. Scott Amerson), and will document the results of QA testing. It is assumed that all bugs have been documented by the programming group as issues before handing off to QA.

Steps involved in the test process will be varied depending on the given test performed (as described below in the Test Cases section).

TEST CASES

PRELIMINARY TESTS

Case 0 #Access,Login Test Cases

Case 0a

Test Results 0a

Would yield an example Summary Test Result of:

Case 0b

Test Results 0b

Would yield an example Summary Test Result of:

Case 0c

Test Results 0c

Would yield an example Summary Test Result of:

Case 0d

Test Results 0d
For scenario 0d, the following actions:

Would yield an example Summary Test Result of:

All Results for Case 0

USERDIRECTORYPROVIDER TESTS

Case 1 #UserDirectorProvider Test Cases

Test Results, Case 1a WebDav

Would yield an example Summary Test Result of:

results: Recorded in Jira http://jira.ucdavis.edu:8080/jira/browse/SAK-154

Test Results Case 1b, User Lookup functionality

Would yield an example Summary Test Result of:

results: Recorded in Jira http://jira.ucdavis.edu:8080/jira/browse/SAK-155

GROUPPROVIDER TESTS

Case 2 #GroupProvider Test Cases

Test Results Case 2a, Tab functionality

Would yield an example Summary Test Result of:

results: Recorded in Jira http://jira.ucdavis.edu:8080/jira/browse/SAK-156

Test Results Case 2b, Realm refresh functionality

Would yield an example Summary Test Result of:

results: Recorded in Jira http://jira.ucdavis.edu:8080/jira/browse/SAK-132

COURSEMANAGEMENTPROVIDER TESTS

Case 3 #CourseManagementProvider Test Cases

Possible Test Data

Case 3a, Roster Update Tests

Test Results Case 3a(1),3a(2), Roster Add functionality

Would yield an example Summary Test Result of:

results: Recorded in Jira http://jira.ucdavis.edu:8080/jira/browse/SAK-124

Case 3b, Roster View Tests

Recording Results

The test results will be recorded in Jira by QA testers. They can be of table form or text form.

Feedback Mechanism

The above results will be analyzed by the QA team, SmartSite programming team, and SmartSite management to determine the quality of code. Results of this test should be discussed as near to the Monday and/or Code Migration meetings when available.