Versions Compared

Old Version 128

changes.mady.by.user Scott Amerson

Saved on

compared with

New Version 129

changes.mady.by.user Scott Amerson

Saved on

Key

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

...

  • 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 (Sakai-dev for integration testing) database will be a either a clean copy or a copy of existing production data, so sakai-test will have to be backed up prior to testing,
    Pradhu or Geeta will be contacted to schedule this. Sakai-dev has been scheduled to be a blank db as of 9/14/06, 2pm.
  • We will be referencing sakai-test (banner test external, mViews..) for populating course data

...

Note
titleSetup Test Case Scenario 0d, Logging into test server via SmartSite's internal admin account, seeing necessary tools

Description = Test the capability of the user to log into the test server using a valid SmartSite admin account and see SU Tool, and other admin functionality

Category of Testing = functionality,regression

Prerequisite Steps
User has valid admin account name, password known

Test Scenario 0d

  1. go to http://sakai-test.ucdavis.edu/portal/xlogin in your browser
  2. user will enter username and password given
  3. User will use admin account name
  4. View site information for a given site (e.g. see Sites link in Admin workspace)
  5. User will logout of admin account
  6. User will use QAAdmin QAadmin account name
  7. Become a user using SU Tool
  8. Logout of using SU Tool

Test Cleanup
None

...

Test

User

User Acting As

Result

Expected Result

Pass/Fail

Login to SmartSite, SmartSite admin account

Pat Kava

admin

logged in, user in "Users Present"

logged in, name in "Users Present"

P

Login to SmartSite, SmartSite admin account

Pat Kava

admin

see admin workspace

see admin workspace

P

Login to SmartSite, SmartSite admin account

Pat Kava

admin

see Sites link

Sites link accessable

P

Logout of SmartSite, using logout link

Pat Kava

admin

logout happens

logout happens

P

Login to SmartSite, using QAAdmin QAadmin account

Pat Kava

QAAdminQAadmin

logged in, user in "Users Present"

logged in, name in "Users Present"

P

See SU page link

Pat Kava

QAAdminQAadmin

SU page/tool available

SU page/tool accessable

P

SU as some instructor using SU Tool

Pat Kava

QAAdminQAadmin

SU by "View User Info" first, then "Become User"

SU happens correctly, become user

P

Logout of SmartSite, using logout link

Pat Kava

SU'd person

logout happens

logout happens

P

...

Note
titleCase 3a, Roster View Test

Description = Test the capability of the CourseMangementProvider to accurately reflect within the SmartSite UI, the roster from a site administrator perspective

Category of Testing = functionality,regression

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

Info
titleCase 3a, Roster view, admin or instructor

Test Scenario, Case 3a

  1. SU as instructor as given by Case 0d, and for this case use calymoskerberos name palmer.
    Data Used

    CRN Type

    Term code - crn

    enrollment

    instructor kname

    Course info

    Term

    CRN with enrollment

    2006-10-32457

    5

    palmer, (Joaquim Silvestre)

    MGP,223,001,Power and Influence

    Fall Quarter 2006

    roster to be given
  2. Verify roster is same as given
  3. Do same as above for the admin user. Note, if the admin user is not a member of the site, then you will not see a tab. You will need to go to "WorkSite Setup" and click "Revise" to see roster information.

...