Release Acceptance Test Plan - pulibrary/pul_library_drupal GitHub Wiki

• Deploy the branch you want to deploy to the staging environment.
• Load the Homepage: https://library-staging.princeton.edu/
• Load a webform that submits email: https://library-staging.princeton.edu/ask-us. Submit the form and look for any errors.
• Run an "all" search. https://library-staging.princeton.edu/find/all/cats. Look for any 500 errors on the browser console from the discovery utils application with the URL base of: https://library-staging.princeton.edu/utils/. If you see one check the web logs for errors from that application.
• Check the databases A to Z page: https://library-staging.princeton.edu/research/databases, browse the letters, if you see results it means the Drupal "views" module is working.
• Check an individual database page: https://library-staging.princeton.edu/resource/11734. Click the access resource button. If this is working you should be forced to login via EZproxy or if you have an active SSO you should see a vendor webpage with a URL that includes the ezproxy information. For this resource that is: https://www-proquest-com.ezproxy.princeton.edu/socialsciences/advanced?accountid=13314.
• Run a database search from https://library-staging.princeton.edu/research/databases. If you see results https://library-staging.princeton.edu/research/databases/search/science it means Drupal's solr search integration is working.
• Test a webform: https://library-staging.princeton.edu/ask-us. If it submits without error webforms with email submissions are working.
• Test a branch landing page: https://library.princeton.edu/lewis.
• Log in to the site as an administrator
• Check the general status report at https://library-staging.princeton.edu/admin/reports/status. Look for any red error rows to investigate further.
• • Check the version of PHP
• • Check to make sure that the application is connecting to solr.
• Edit a record. Visit https://library-staging.princeton.edu/admin/content. Select a "basic page" content type to edit. Make an edit in the main html body section of the record. Save the record. Remove your change, save the record again.
• Add an image to a record. Visit a content type that has an image field attached to it like a library news item. Download a copy of the stories featured graphic. Remove that graphic, save the news item. Add the image back and save the graphic you saved locally.
• Test the ability of solr to index records. Visit https://library-staging.princeton.edu/admin/config/search/search_api. Select the staff user index https://library-staging.princeton.edu/admin/config/search/search_api/index/staff_users.
• • Select the option to "clear all indexed data". This will drop the staff index from solr.
• • https://library-staging.princeton.edu/staff/directory will be empty
• • Re-index the content at https://library-staging.princeton.edu/admin/config/search/search_api/index/staff_users by selecting the option to "Index All Now". A dialog showing indexing progress will run. It will take 15-20 seconds.
• • https://library-staging.princeton.edu/staff/directory will have user names displayed again.

If you encounter any error messages testing the above pages consult the watchdog log at: https://library-staging.princeton.edu/admin/reports/dblog. Filter to just "errors"

Watchdog can also be consulted at the command line view drush using the "watchdog-show" command.