Back to Milestone 5
The following is a list of test cases, identified by number:
Open fresh web browser to calendar URL. All approved events should display in ascending start date/time order. No event add/modify/delete requests should be seen.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST1, then click on one of the events on the calendar. The event clicked should be shown in detail. Check to make sure information is accurate, and agrees with information on calendar page. There should be links to request modifications or deletes. Submitter information should not be visible.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST2, then change the URL so the number that follows EventID= is an invalid number or a valid number but for a record that does not exist. Expected result is an error message saying the event was not found.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST1, then click "Add Event" from the navigation bar. The page shown should say "request addition to calendar" and provide input elements for all the fields of a calendar event. There should be a button to submit the requested event. The user must enter an event name and starting date, as well as submitter name and email. After the submit, the user should be presented with "Your request has been recorded successfully and will take effect pending administrative approval."
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST2, then click "Edit Event." You should see a page that says "request changes to an event on the calendar" which provides input elements for all the fields of a calendar event except submitter information. There will be blank inputs for submitter information that the user is required to fill out before submitting the modification request. After the submit, the user should be told "Your request has been recorded successfully and will take effect pending administrative approval." Check with administrator login that request appears on "Review Event Requests" page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Repeat TEST5 on the same event. Check using the administrative login that both modification requests appear on the "Review Event Requests" page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST2 on any event, then click "Delete Event." You should see a form, "Request removal of an event from the calendar," for entering required submitter information. Once submitted, the user should be told "Thank you for your request. It will need to be approved before the calendar is updated." Check with administrator login that delete request appears on "Review Event Requests" page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Repeat TEST7 with the same event. Check with administrator login that both delete requests appear on the "Review Event Requests" page. Approve the first delete request and check the calendar to see that the event was deleted. Also check that approving the second delete request removes the request from the queue and causes no errors.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Login as administrator, go to "Review Event Requests" page and create a bookmark. Then click Logout. Clear the cache by closing and re-opening your browser. Then go to the saved bookmark. You should see be redirected back to the login page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Go to the login page URL and enter incorrect password. After submitting, the login page will be displayed again with an error message saying "incorrect password." This time enter correct password and submit. The "Review Event Requests" page will be displayed.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Repeat TEST1 while logged in. Calendar display should appear exactly the same as it did in TEST1.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Repeat TEST2 while logged in. In addition to info displayed in TEST2, the original submitter information should be displayed. In addition, the commands available will be "edit event" and "delete event."
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Click "Review Event Requests". You will see a list of event requests that have been submitted. Clicking on an event name will display details about that request and commands to approve or reject the request. The list should also display what type of request it is (add/modify/delete).
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST13, and click on a new event request. Choose Approve. Check the "Review Event Requests" page again to verify that the request no longer displays on the list. Check the "calendar" page to verify that the new event is now displayed in the proper order.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST13, and click on an event modification request. Choose Approve. Check the "Review Event Requests" page to verify that the request is no longer displayed. Check the "calendar" page and the original event page to verify the information has been updated.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST13, and click on an event removal request. Choose Approve. Check the "Review Event Requests" page to verify that the request is no longer displayed. Check the "calendar" page to verify the event has been removed.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST13, and click on a new event request. Choose Reject. Check the "Review Event Requests" page to verify that the request is gone. Check the "calendar" page to verify that no events have been added.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST13, and click on an event modification request. Choose Reject. Check the "Review Event Requests" page to verify that the request is gone. Check the "calendar" page and the original event page to verify that the event has not changed.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST13, and click on an event removal request. Choose Reject. Check the "Review Event Requests" page to verify that the request is gone. Check the "calendar" page and the original event page to verify that the original event is still intact.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Login as administrator and click "add event" from the navigation bar. A blank event form should be displayed, minus the submitter information. Fill it out and submit. Check the calendar to verify that the event was immediately added. Check the "Review Event Requests" page to verify that no request was generated.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST12, and click "edit event." Enter new information and click Submit. Check the calendar and the original event page to verify that the event was immediately updated. Check the "Review Event Requests" page to verify that no request was generated for the edit.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST12, and click "delete event." No additional information should be required. The page should verify (Yes/No) that the user wants to do it. First click No and make sure event was not deleted. Then try again clicking Yes. Check the calendar and verify that the event was removed. Check the "Review Event Requests" page and make sure no removal request was generated.
Date: 4/28
Result: FAIL
No yes/no option shown before delete.
Date: 5/02 Result: Pass
Go to add page and leave form blank to submit. An error message should appear complaining about one or more fields being empty. Fill in the mentioned fields and repeat. An additional error message may appear. If so, repeat until no error message appears. Go to the view event page and verify that the event displays only the information added, and displays it correctly.
Date: 5/02 Result: Pass
Create a bookmark to the add contact page by logging in as administrator, going to add contact, and saving a bookmark. Then logout and go to the bookmark as a public user. Expected result is a redirect to the login page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
After adding a contact, save a bookmark to the URL that displays the contact. Do logout and return to the same URL. You should see all contact information except internal comments.
Date: 5/02 Result: Pass
Start with TEST25, and modify the URL so that the part after ContactID is no longer a valid contact ID. You should see a "contact not found" error message.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Create a bookmark to the edit page of a contact, logout, and go to the bookmarked location. You should be redirected to the login page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Login and view a contact. You should see all information, including internal comments. You should also see links that can be clicked on to edit the current contact and delete the current contact.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Login and click "add contact." You should see an empty form with an input element for each field of the contact. Submit and you should see the view contact page for the new contact. After the submit, the user should be presented with "Changes recorded successfully."
Date: 5/02
Result: FAIL
Does not display confirmation message
Date: 5/02 Result: Pass
Login and view a contact. Click "edit this contact." You should see a form with input elements for each field of the contact, with the current contact information filled in. Submit and you should see the updated view contact page. After the submit, the user should be presented with "Changes recorded successfully."
Date: 5/02
Result: FAIL
does not display confirmation message
Date: 5/02 Result: Pass
Go to add contact and submit with an empty form. You should receive one or more error messages for empty fields. Correct these by filling in something in those fields. Repeat until no more error messages are seen. You are now on the view contact page. Make sure everything shows up correctly.
Date: 4/28
Result: FAIL
Phone numbers appeared as '--' instead of being ommitted completely.
Date: 5/02 Result: Pass
Create a bookmark to the add resource page by logging in as administrator, going to add resource, and saving a bookmark. Then logout and go to the bookmark as a public user. Expected result is a redirect to the login page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
After adding a library resource, save a bookmark to the URL that displays the resource info. Do logout and return to the same URL. You should see all resource information.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Start with TEST33, and modify the URL so that the part after ResourceID is no longer a valid resource ID. You should see a "resource not found" error message.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Create a bookmark to the edit page of a library resource, logout, and go to the bookmarked location. You should be redirected to the login page.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Login and view a resource. You should see exactly the same information as a public user can see. You should also see links that can be clicked on to edit the current resource and delete the current resource.
Date: 4/28 Result: Pass
Date: 5/02 Result: Pass
Login and click "add resource." You should see an empty form with an input element for each field of the library resource. Submit and you should see the view resource page for the new resource. After the submit, the user should be presented with "Changes recorded successfully."
Date: 5/02
Result: FAIL
Does not display confirmation message
Date: 5/02 Result: Pass
Login and view a resource. Click "edit this resource." You will see a form with input elements for each field of the resource, with the current resource information filled in. Submit and you should see the updated view resource page. After the submit, the user should be presented with "Changes recorded successfully."
Date: 5/02
Result: FAIL
Does not display confirmation message
Must have both first and last name to print, will not print just one
Date: 5/02 Result: Pass
Go to add resource and submit with an empty form. You will receive one or more error messages for empty fields. Correct these by filling in something in those fields. Repeat until no more error messages are seen. You are now on the view resource page. Make sure everything shows up correctly.
Date: 5/02 Result: Pass
Click on the "Search" link in the navigation bar. You will see the search page where you can search by keyword(s) in Calendar, Contacts, and Library.
Date: 5/02 Result: Pass
Start with TEST40 and make sure that all three data options are selected. Click the Search button to search without a keyword. The search will return results on the Search Results page of all records contained in the Calendar, Contacts, and Library, grouped by the different data sources. If there are no matches, "No records found." will appear under the corresponding data source title.
Date: 5/02 Result: Pass
Start with TEST40 and run a search with no keywords and for each data source individually, and then in pairs. The result will be the Search Results page with a list of all records for the corresponding selected data source. If there are no matches, "No records found." will appear under the corresponding data source title (for each data source that was selected before performing the search).
Date: 5/02 Result: Pass
Start with TEST40 and run a search with none of the data sources selected. The result will be an empty Search Results page with no errors.
Date: 5/02 Result: Pass
Start with TEST40, enter one or more keywords into the "Enter your search term(s)" box and run a search. The result will be the Search Results page with corresponding titles for each data source selected before the search. Results that have a match with the keyword(s) searched will be displayed under the title of the data source where the record is located. If there are no matches for a data source, "No records found." will appear under the title of the data source.
Date: 5/02 Result: Pass
Login and click the "Search" link in the navigation bar. You will see the search page where you can search by keyword(s) in Calendar, Contacts, and Library.
Date: 5/02 Result: Pass
Run searches based upon each of TEST41, TEST42, TEST43, and TEST44.
Date: 5/02 Result: Pass
On the server computer, change the name of the data source. This will help us to weed out any places in the code where the DSN "Gender" is hard-coded.
Date: 5/05 Result: Pass
|
| Page Execution took real: 22.571, user: 15.290, sys: 0.780 seconds |