Primo VE (UC Library Search) Test Plan Best Practices

Getting started

  1. What changes are we talking about? 
    1. Changes recommended by UC-wide Discovery Functional Group (DFG) to Primo VE
      1. UI and/or general functionality
    2. Changes suggested by staff and approved by the UCB SILS Implementation Team and/or the Alma/Primo VE Management Team
      1. Pending requests are triaged in the Primo VE enhancement request list
  2. Changes will be moved into production
    1. Preferred: Monday - Wednesday
    2. In a pinch: Thursday
    3. Only if crisis: Friday
  3. Who is involved in the process?
    1. S&DS will make the configuration changes for Primo VE outside of the customization package
    2. LCO/Web  will make configuration changes for Primo VE in the customization package
    3. LCO/Web  and Web team will test changes
  4. Who will test each change and how?
    1. S&DS will test configuration changes in the Premium Sandbox Environment 
      1. Will request data stakeholders to confirm expected behavior
      2. Other groups (such as WAG, PSC) may be involved, as decided by the UCB SILS Alma/Primo VE Coordination Team
    2. Public and lending Macs include Safari, Chrome, and Firefox. Staff Macs include Safari and Chrome (Firefox can be installed via BigFix). LCO/Web  will test changes:
      1. MacOS on desktop computer
        1. Safari, Chrome, and Firefox
      2. iOS on iPhone
        1. iOS versions of Safari, Chrome, and Firefox
      3. BrowserStack
        1. Desktop PC versions of Chrome, Firefox, and Edge
        2. Android devices: Chrome and Firefox
    3. Web team will test changes on her laptop that runs Windows 10.
      1. Use the current versions Chrome, Firefox, and Edge.
        1. Research public PCs include Chrome
        2. Staff PCs include Chrome and Edge.
          1. Firefox can be installed via BigFix.
      2. Also test previous browser versions via Browserstack.
    4. Web team will test changes on her Android phone.
      1. Use the current version of Chrome.
      2. Also test Chrome on other recent Android versions via Browserstack.
  5. Errors found during testing will be reported on the #primo slack channel for troubleshooting
    1. LCO/Web  will investigate if a fix available in the customization package
    2. S&DS will open an ExLibris Support Ticket, if applicable
  6. Change must be made at least 3 days before the lead person making the change goes on vacation.
  7. What is the plan if there is a problem?
    1. If functionality is not adversely affected and the person who made the change will be back at work within a few days, the problem can wait until their return.
    2. If functionality is adversely affected and there is another staff person who can address the problem, it will be addressed while the person is away from work.
    3. If functionality is adversely affected and there is not another staff person who can address the problem, but one who can back out the change, the change will be backed out.

Checklist for changes, new functionality, and some stylesheet changes:

  1. Does it work?
    1. Browser and OS testing
      1. Test actual devices where possible
      2. Test in Browserstack where actual devices and/or versions are not available
  2. Did it break anything?
    1. Are things lining up and in their “right” spots?
    2. Are all buttons not overlapping with other buttons or functionality? 
    3. Do things wrap as intended?
    4. Did you introduce any thing that doesn’t seem to “fit”? 
  3. Are the fonts consistent across the site?
  4. Is the terminology used consistent across the site?
  5. Is it responsive?
    1. Test actual devices where possible
    2. Test in Browserstack where actual devices are not possible
  6. Is it accessible?
    1. Run through WAVE
    2. Alt text
    3. Color contrast
    4. Form labels
    5. Keyboard test
    6. Descriptive links
    7. Headings depict hierarchy
    8. Meaningful error messages
    9. Other accessibility tools (HTML Sniffer, Accessibility Insights for Web)
  7. If new app:
    1. Is there a favicon?
    2. Does the branding match the Library’s color palette 

By gosselar on 09-12-2023

Tags

Policy