Skip Navigation Bar

Web Site/Applications Quality Assurance Check List

  1. Section 508 compatibility review
    • If desired, National Library of Medicine (NLM) Office of Computer & Communications Systems (OCCS) support must be arranged 4 weeks prior to final delivery of product.
  2. CGI script review by OCCS Web Support Team
    • Prior to development, OCCS should be consulted for general guidance. OCCS support must be arranged 4 weeks prior to final delivery of product for final CGI review.
  3. Database design review by DBA team
    • Prior to development, OCCS should be consulted for general guidance. OCCS support must be arranged 4 weeks prior to final delivery of product for final CGI review.
  4. Content review by functional user group
    • User group is responsible for Quality Assurance of delivered content by a third party.
  5. Define target web browsers and versions to be supported
    • Each browser/platform supported must be fully tested using test plan.
    • Includes section 508 related browsers (JAWS, etc.).
  6. Quality assurance test plan created
    • Testing should include:
      • Pages “look and feel” is as specified.
      • Page content is correct and accurate.
      • Forms based controls and fields correct and operating to specification.
        1. Fields contain correct “canned” data (data pre-populated in the form) if applicable;
        2. Error correction and detection is in place and as specified;
        3. Error messages to user are as specified;
        4. Testing should include invalid values submitted in fields and application response;
        5. Testing should include iterative use of form fields to see all possible behavior of application when fields are empty or have invalid data;
        6. Include testing of all button controls – buttons should behave as specified;
        7. User should be returned to most logical page after a form submission.
      • Data integrity check.
        1. Adding/updating/deletion of data should be validated;
        2. Retrieval of data after add/update/delete should be validated (similar to above);
        3. Iterative updates to data – updating same data piece more than once – should show data was changed each time.
      • Data privileges check.
        1. For applications that contain user privilege levels, ensure that only users with proper privileges may access restricted areas of application;
        2. Ensure that login integrity is maintained. That a user must be logged into the application in order to use ANY of its pages. I.E. User cannot enter a URL of the application and go directly to the page without already having been logged into the application.
      • Site navigation.
        1. No broken links.
          • All links have correct target specified and all links take user to the target when clicked;
          • Required NLM links are present and operational in headers and/or footers.