2.4 Function Integration Tests

Display Email Not Kerberos Name Test

SAK-626

The UCD Sakai team has modified our code so each user's email address is displayed in the User Id fields rather than the user's Kerberos name. The email name is the first part of the email address before the "@ucdavis.edu". For many UCD faculty, staff, and students, both names are the same; for others, the Kerberos name is radically different and difficult to associate with an individual. Just ask peon or nuchickn.

Test Setup
For our QA group, only Brian has the same email as Kerberos name. For the purpose of this test, I'm including our email names and what to check for here:

If you do not have all the tools available to you activated, please add them as needed for this test. You may need other testsers to interact with you to complete this test.

Test Steps
Access the following tools as noted and verify that the user's email name is displayed as the User or Student Id - not his/her Kerberos name. If you run into other issues with this test, please shoot me an email as we're checking tools previously untested.

Reporting instructions: Report the test step where the User or Student Id does NOT appear in email format. Do not report a fail or pass as we need to determine if any exceptions are actually okay.

Report your results to: SAK-626

Site Info Mailid Test

SAK-645

This test series is designed to address multiple issues in SmartSite with manually adding users to a course via Site Info.
The test requires that you enter both valid and invalid UCDavis mailIDs, email addresses, and Kerberos IDs. A mailid is just the username portion of a UC Davis mail account without '@ucdavis.edu'. For some users, the mailID and Kerberos are the same; for others, the two are different. Invalid data would be any email account outside of the UCDavis sphere, for example, your gmail account which is invalid for UCD authentication. To come up with invalid mailIDs and Kerberos IDs, you may need to use your imagination!

To come up with valid user data for testing, you can find user accounts at http://www.ucdavis.edu/cgi-bin/whois. Try entering a common last name to find accounts where the mailID and Kerberos ID differ.

First run-through: all valid users assigned the same role

1. Log in to a course site as an instructor.
2. Select Site Info from the course menu and then select 'Add Participants' from the Site Info tool menu.
3. On the 'Add Participants to...' screen under the 'Username(s)' textbox, enter one or more valid UC Davis mail ids, email addresses, or kerberos ids.
4. Select the radio button below that says 'Assign all participants to the same role'.
5. Press the 'Continue' button and verify that the screen 'Choose a Role for Participants' is loaded and the default Roles of Instructor, Student, and Teaching Assistant are listed as options and the user's Kerberos IDs for the users you entered are listed under Participants.
6. Do not select any roles and press the 'Continue' button. Verify that you receive a acreen alert and are not allowed to continue.
7. Select a role and press the 'Continue' button. Verify that the screen 'Add participant(s)...' is loaded giving you the option to send or not send an email notification.
8. Make a notification selection (only select notify if you're using other tester accounts!) and then select 'Continue'. Verify that the screen 'Confirming Add Participant(s) to...' is loaded and that you see each of the valid users listed with their full name, kerberos id, and the same role.
9. Press the 'Finish' button. Verify that the users you added are now listed in the site roster with the role that you selected for them.

Second run-through: all valid users assigned different roles

1. Repeat steps 2-3 from the first test and then select the radio button below that says 'Assign each participant a role individually'.
2. Press the 'Continue' button and verify that the screen 'Choose a Role for Participants' is loaded and that the default Roles of Instructor, Student, and Teaching Assistant are displayed with text descriptions. Verify that each user's Kerberos ID is listed and has a drop-box under Roles.
3. Leave one or more of the drop boxes with a role unselected and press the 'Continue' button. Verify that you receive an alert and are not allowed to continue, and that the roles you did select for some users are unchanged.
4. Select a role for each user and press the 'Continue' button. Verify that the screen 'Add participant(s)...' is loaded giving you the option to send or not send an email notification.
5. Make a notification selection (only select notify if you're using other tester accounts!) and then select 'Continue'. Verify that the screen 'Confirming Add Participant(s) to...' is loaded and that you see each of the valid users listed with their full name, kerberos id, and different roles.
6. Press the 'Finish' button. Verify that the users you added are now listed in the site roster with the role that you selected for them.

Third run-through: some invalid users

1. Repeat steps 2-3 from the first test, but include some invalid mailIDs, email addresses, or KerberosIDs along with at least one valid user datum. Verify that you receive an alert message and are not allowed to continue until you remove all invalid user data. Once the invalid data is removed and you can press the 'Continue' button successfully, you can stop this run-through.

Fourth run-through: all invalid users

1. Repeat steps 2-3 from the first test, but include only invalid mailIDs, email addresses, or KerberosIDs. Verify that you receive an alert message and are not allowed to continue until you remove the invalid user data. Verify that you receive a different alert when trying to press the 'Continue' button with no users listed.

Fifth run-through: duplicate users

1. Repeat steps 2-3 from the first test, but this time include one or more users with duplicate user data. For example, enter both a valid mailIDs, email addresses, and/or KerberosIDs for a single user. Select user data where the mailID and Kerberos ID's are either the same or are different.
2. Press the 'Continue' button and verify that the screen 'Choose a Role for Participants' is loaded and that you receive an alert which lists the Kerberos ID for each duplicate user data entered. Verify that the user data you entered are limited to just the user's Kerberos IDs. You can now stop this run-through.

Final run-through: test Back and Cancel functions

1. Repeat the first test, but use the Back or Cancel button throughout the process to verify that neither function is impaired.

Post your test results indicating either a pass or a fail with details to: SAK-645

Contact Us Test

SAK-653

Contact Us integrates functionality between SmartSite and Remedy. The integration tests will be scheduled for a particular date and time to allow programmers from both systems to verify that it functions as specified.

Scheduled Test Date/Time: Wednesday, June 13, 11:00am

Test 1: Contact Us from SmartSite login screen

1. Go to the login screen, but do not log in. Click on the Contact Us button and verify that a new window opens.
2. Verify that the new window displays the IT Express Contact Us form which includes Summary and Description data entry fields and a Submit button.
3. Verify that the text is spelled correctly and makes sense to the user.
4. Verify that the Contact Us link returns the user to the same form (link is useful for other systems - although redundant here it must not break.)
5. Verify the UCD link sends the user to UC Davis website.
6. Verify the IET link sends the user to the IET website.

Test 2: Contact Us from specific tool

This test verifies that the proper information is being sent to the Remedy system. Split up the list of Smartsite tools amongst available testers so that we're not flooded with too much data.
Remedy options listed, but not included in this test are: Authentication, SCORM, Site Request, Undetermined, Web Development, WebDav

1. To prepare, cut and past the following table into a Word doc or use this Excel table.
2. Log in and navigate to each tool listed in the description. Add the tools if necessary to access all the tools in the list. You are encouraged to access different sites for some of these tools as well, although you only need to test Contact Us from each tool once.
   • Note: Test Message Center (from existing courses) AND Messages and Forums from a new course, if possible.
3. After accessing the tool, select the Contact Us button and verify the new window opens.
4. Enter/cut & paste the text in the following table in the fields specified; do not deviate from this test as we're verifying that the correct information is reported to the correct fields from SmartSite to Remedy.
5. Select Submit to send your message.
6. When you receive the onscreen response, note the ticket or case number at the end of the message. Write that number down in the Word or Excel file next to the tool you are testing.
7. From a tool of your choice, select Contact Us. Select the Contact Us link at the top of the form. Enter " Testing Contact Us Refresh" in the Summary and the name of the tool you accessed in the Description fields. Write down the case/ticket number after submission.
8. Log out and select Contact Us again. Enter "Testing Undetermined" in the Summary and "Not Logged in" in the Description fields. Write down the case/ticket number.

When you complete this portion of the test, attach your .doc or .xls file to the Jira. Your results will be forwarded to the IET Remedy team rep for review to determine if we are getting the desired results.

Post your Test 1 test results and attachment to: SAK-653