Page Comparison

Description = Test the capability of the UserDirectoryProvider to provide information about an externally provided user via the SU Tool

Category of Testing = functionality,regression

Prerequisite Steps

1. SU tool available to tester

Test Scenario 1b, User lookup functionality

1. Log in as any user having administrative access (access to admin realm)
2. Use a given kerberos name available via test data (e.g. instructor)
3. Enter kerberos name, and click "View User Info"
4. Verify user information from whois.ucdavis.edu and/or email.ucdavis.edu

• Data to Be Used:
  QA determines

Test Cleanup
None

Description = Test the capability of the GroupProvider to provide tabs for a user based on their enrollment/membership in sites

Category of Testing = functionality,regression

Prerequisite Steps

1. Site user is a member of must be already created prior to test (via Batch)
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 2a, Tabs

1. Log in as in Case 0d, but become the user and don't log out
2. Log in instructor for a given site site (see test data attachment)
3. View tabs presented for sites available, and only those that you are a member of and have been created will appear
4. Stay logged in for case 2b

-Additional step for programmers (Case 2ai), verify that data presented in tabs matches server log data-

• Data to Be Used:
  QA determines

Test Cleanup
None

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)
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 or Scott Amerson 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